[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260122134145-GYE63789@gentoo.org>
Date: Thu, 22 Jan 2026 21:41:45 +0800
From: Yixun Lan <dlan@...too.org>
To: Mark Brown <broonie@...nel.org>
Cc: Guodong Xu <guodong@...cstar.com>, Liam Girdwood <lgirdwood@...il.com>,
Alex Elder <elder@...cstar.com>, Lee Jones <lee@...nel.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Troy Mitchell <troy.mitchell@...ux.spacemit.com>,
Paul Walmsley <pjw@...nel.org>, Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>, Alexandre Ghiti <alex@...ti.fr>,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
spacemit@...ts.linux.dev, devicetree@...r.kernel.org
Subject: Re: [PATCH 0/4] regulator: spacemit-p1: Fix voltage ranges and
support board power tree
Hi Mark,
On 13:28 Thu 22 Jan , Mark Brown wrote:
> On Thu, Jan 22, 2026 at 08:12:23PM +0800, Yixun Lan wrote:
> > On 11:27 Thu 22 Jan , Mark Brown wrote:
>
> > > Patch 1 looks like it should be OK as is?
>
> > then with patch 3, and for other boards (milkv jupiter), should have similar
> > DT fix as patch 4..
>
> Yes, changing the supply names would at a minimum need all the boards
> updating (it's an ABI change so shouldn't really happen, but perhaps
> there are few enough users for everyone to coordinate and it's what you
yes, that's what I care..
> all prefer). Patch 1 shouldn't have any effect unless a board already
> specifies a wider range than the driver currently supports.
I realized you were talking about patch 1 only, and plan to take it?
then yes, please feel free to do it..
--
Yixun Lan (dlan)
Powered by blists - more mailing lists