linux-kernel - Re: [PATCH] ARM: omap: pmic-cpcap: do not mess around without CPCAP or OMAP4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <174433227218.2416322.15261895858877666275.b4-ty@baylibre.com>
Date: Thu, 10 Apr 2025 17:44:32 -0700
From: Kevin Hilman <khilman@...libre.com>
To: khilman@...nel.org, aaro.koskinen@....fi, rogerq@...nel.org, 
 tony@...mide.com, linux@...linux.org.uk, linux-omap@...r.kernel.org, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, 
 sre@...nel.org, Andreas Kemnade <andreas@...nade.info>
Cc: stable@...r.kernel.org
Subject: Re: [PATCH] ARM: omap: pmic-cpcap: do not mess around without
 CPCAP or OMAP4


On Mon, 31 Mar 2025 16:44:39 +0200, Andreas Kemnade wrote:
> The late init call just writes to omap4 registers as soon as
> CONFIG_MFD_CPCAP is enabled without checking whether the
> cpcap driver is actually there or the SoC is indeed an
> OMAP4.
> Rather do these things only with the right device combination.
> 
> Fixes booting the BT200 with said configuration enabled and non-factory
> X-Loader and probably also some surprising behavior on other devices.
> 
> [...]

Applied, thanks!

[1/1] ARM: omap: pmic-cpcap: do not mess around without CPCAP or OMAP4
      commit: 7397daf1029d5bfd3415ec8622f5179603d5702d

Best regards,
-- 
Kevin Hilman <khilman@...libre.com>