linux-kernel - Re: (subset) [PATCH] mfd: sec: Use chained IRQs for s2mpg10

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: <176363458726.601076.17998415477527766315.b4-ty@kernel.org>
Date: Thu, 20 Nov 2025 10:29:47 +0000
From: Lee Jones <lee@...nel.org>
To: Krzysztof Kozlowski <krzk@...nel.org>, Lee Jones <lee@...nel.org>, 
 André Draszik <andre.draszik@...aro.org>
Cc: Peter Griffin <peter.griffin@...aro.org>, 
 Tudor Ambarus <tudor.ambarus@...aro.org>, 
 Will McVicker <willmcvicker@...gle.com>, Juan Yescas <jyescas@...gle.com>, 
 Douglas Anderson <dianders@...omium.org>, kernel-team@...roid.com, 
 linux-kernel@...r.kernel.org, linux-samsung-soc@...r.kernel.org
Subject: Re: (subset) [PATCH] mfd: sec: Use chained IRQs for s2mpg10

On Fri, 14 Nov 2025 14:10:59 +0000, André Draszik wrote:
> On S2MPG10 (and similar like S2MPG11), top-level interrupt status and
> mask registers exist which need to be unmasked to get the PMIC
> interrupts. This additional status doesn't seem to exist on other PMICs
> in the S2MP* family, and the S2MPG10 driver is manually dealing with
> masking and unmasking currently.
> 
> The correct approach here is to register this hierarchy as chained
> interrupts, though, without any additional manual steps. Doing so will
> also simplify addition of other, similar, PMICs (like S2MPG11) in the
> future.
> 
> [...]

Applied, thanks!

[1/1] mfd: sec: Use chained IRQs for s2mpg10
      commit: ee19b52c31b3b111f140c1affd88eca1ed11edd0

--
Lee Jones [李琼斯]