linux-kernel - Re: (subset) [PATCH v2] mfd: axp20x: set explicit ID for regulator cell if no IRQ line is present

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: <175213766092.1425808.13168630875938700813.b4-ty@kernel.org>
Date: Thu, 10 Jul 2025 09:54:20 +0100
From: Lee Jones <lee@...nel.org>
To: Lee Jones <lee@...nel.org>, Chen-Yu Tsai <wens@...nel.org>
Cc: Chen-Yu Tsai <wens@...e.org>, linux-sunxi@...ts.linux.dev, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, 
 Andre Przywara <andre.przywara@....com>, 
 Chris Morgan <macroalpha82@...il.com>, 
 Vasily Khoruzhick <anarsoul@...il.com>
Subject: Re: (subset) [PATCH v2] mfd: axp20x: set explicit ID for regulator
 cell if no IRQ line is present

On Wed, 02 Jul 2025 00:36:52 +0800, Chen-Yu Tsai wrote:
> Originally an explicit ID for the AXP313/AXP323 regulator was set to
> avoid a conflict with the primary AXP717 PMIC on Allwinner A523 family
> boards.
> 
> This didn't entirely work since on some or all of these boards, the
> interrupt line on this secondary PMIC was left unconnected, and thus
> the driver would fall back to the generic "no interrupt; only regulators"
> case, which didn't have the explicit ID set, thus undoing the intended
> fix.
> 
> [...]

Applied, thanks!

[1/1] mfd: axp20x: set explicit ID for regulator cell if no IRQ line is present
      commit: c6c68f08d524ab76cc3cf6449a8cb235b8c3fc06

--
Lee Jones [李琼斯]