[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <684ee927-2287-420b-aee5-f323e05ada47@hatter.bewilderbeest.net>
Date: Fri, 23 Feb 2024 15:16:26 -0800
From: Zev Weiss <zev@...ilderbeest.net>
To: Conor Dooley <conor@...nel.org>
Cc: linux@...ck-us.net, Conor Dooley <conor.dooley@...rochip.com>,
Jean Delvare <jdelvare@...e.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Patrick Rudolph <patrick.rudolph@...ements.com>,
Peter Yin <peteryin.openbmc@...il.com>,
Alexander Stein <alexander.stein@...tq-group.com>,
linux-hwmon@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Naresh Solanki <naresh.solanki@...ements.com>
Subject: Re: [PATCH v2 4/5] hwmon: (pmbus/lm25066) Use PMBUS_REGULATOR_ONE to
declare regulator
On Fri, Feb 23, 2024 at 08:21:08AM PST, Conor Dooley wrote:
>From: Guenter Roeck <linux@...ck-us.net>
>
>If a chip only provides a single regulator, it should be named 'vout'
>and not 'vout0'. Declare regulator using PMBUS_REGULATOR_ONE() to make
>that happen.
>
As mentioned on Guenter's v1, this change necessitates a corresponding
update to arch/arm/boot/dts/aspeed/aspeed-bmc-delta-ahe50dc.dts, which
has a dependency on the name of the regulator. Given (AFAICT) the lack
of any combined dts & driver patches anywhere in the kernel git history
I guess maybe doing both atomically in a single commit might not be
considered kosher, but could it at least be included in the same patch
series?
Thanks,
Zev
Powered by blists - more mailing lists