linux-kernel - Re: (subset) [PATCH] mfd: axp20x: Set explicit ID for AXP313 regulator

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: <175084255601.4077397.7103143558285168372.b4-ty@kernel.org>
Date: Wed, 25 Jun 2025 10:09:16 +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] mfd: axp20x: Set explicit ID for AXP313
 regulator

On Fri, 20 Jun 2025 01:32:07 +0800, Chen-Yu Tsai wrote:
> On newer boards featuring the A523 SoC, the AXP323 (related to the
> AXP313) is paired with the AXP717 and serves as a secondary PMIC
> providing additional regulator outputs. However the mfd cells are all
> registered with PLATFORM_DEVID_NONE, which causes the regulator cells
> to conflict with each other.
> 
> Commit e37ec3218870 ("mfd: axp20x: Allow multiple regulators") attempted
> to fix this by switching to PLATFORM_DEVID_AUTO so that the device names
> would all be different, however that broke IIO channel mapping, which is
> also tied to the device names. As a result the change was later reverted.
> 
> [...]

Applied, thanks!

[1/1] mfd: axp20x: Set explicit ID for AXP313 regulator
      commit: 77f6b46f199b8a483e0cfa176b7a629f75a2c4c4

--
Lee Jones [李琼斯]