From: Krzysztof Kozlowski <krzk@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>,
"Encarnacion,
Cedric justine" <Cedricjustine.Encarnacion@analog.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jean Delvare <jdelvare@suse.com>,
Jonathan Corbet <corbet@lwn.net>,
Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: hwmon: pmbus: add lt3074
Date: Mon, 24 Mar 2025 08:16:10 +0100 [thread overview]
Message-ID: <7c3f107e-2732-4d6e-a9e4-652ae18c16c5@kernel.org> (raw)
In-Reply-To: <16b6b98e-711e-40d5-970e-af1feb46ce91@roeck-us.net>
On 21/03/2025 18:24, Guenter Roeck wrote:
>>
>> Figured. As it turns out, there is also a patch series pending which tries
>> to fix the problem for ir38060 by changing its bindings.
>>
>> I'll dig up my patch series to add a new macro and send it out as RFT.
>>
>
> Question for DT maintainers:
>
> Existing bindings, such as
> Documentation/devicetree/bindings/regulator/mps,mpq2286.yaml
> expect a nested regulators node even though there is only a single
> regulator. What is the correct approach: Keep the nesting requirement
> for those regulators as is (even if there are no in-tree bindings
> using them), or update the code and the bindings to drop the nesting ?
>
I would recommend keep the nesting, so don't touch it. There might be
external users, other projects relying on this. You can however
deprecate old node (nesting), if the driver can support both. Not sure
if it is worth the effort.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-24 7:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 13:01 [PATCH v2 0/2] Add support for LT3074 low voltage linear regulator Cedric Encarnacion
2025-02-25 13:01 ` [PATCH v2 1/2] dt-bindings: hwmon: pmbus: add lt3074 Cedric Encarnacion
2025-02-26 8:20 ` Krzysztof Kozlowski
2025-02-26 14:59 ` Rob Herring
2025-02-26 19:17 ` Guenter Roeck
2025-02-27 8:50 ` Krzysztof Kozlowski
2025-02-27 16:32 ` Guenter Roeck
2025-03-18 10:03 ` Encarnacion, Cedric justine
2025-03-18 15:17 ` Guenter Roeck
2025-03-19 4:10 ` Encarnacion, Cedric justine
2025-03-21 16:53 ` Encarnacion, Cedric justine
2025-03-21 17:09 ` Guenter Roeck
2025-03-21 17:24 ` Guenter Roeck
2025-03-24 7:16 ` Krzysztof Kozlowski [this message]
2025-03-24 13:58 ` Guenter Roeck
2025-03-21 20:23 ` Guenter Roeck
2025-04-07 22:59 ` Guenter Roeck
2025-02-25 13:01 ` [PATCH v2 2/2] hwmon: (pmbus/lt3074): add support for lt3074 Cedric Encarnacion
2025-02-26 13:03 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7c3f107e-2732-4d6e-a9e4-652ae18c16c5@kernel.org \
--to=krzk@kernel.org \
--cc=Cedricjustine.Encarnacion@analog.com \
--cc=Delphine_CC_Chiu@wiwynn.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox