From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Guenter Roeck <linux@roeck-us.net>,
Conor Dooley <conor@kernel.org>,
Naresh Solanki <naresh.solanki@9elements.com>
Cc: broonie@kernel.org, Jean Delvare <jdelvare@suse.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: hwmon: ir38060: Move & update dt binding
Date: Thu, 13 Feb 2025 10:55:29 +1030 [thread overview]
Message-ID: <27d51c2c498cc5921998829e5279bf136d10f2dc.camel@codeconstruct.com.au> (raw)
In-Reply-To: <c8dc4bdc-5374-4648-8092-55687be85f12@roeck-us.net>
Hi Guenter,
On Wed, 2025-02-12 at 06:46 -0800, Guenter Roeck wrote:
> Hi Andrew,
>
> On 2/12/25 02:43, Andrew Jeffery wrote:
> [ ... ]
> > The history of the problem from what I can see looks like:
> >
> > 1. pmbus regulator support exploiting "regulators" as an OF
> > child
> > node was merged for 3.19[1]
>
> I hope you mean "make full use of and derive benefit from (a
> resource)"
> and not "use (a situation or person) in an unfair or selfish way".
Certainly "make full use of and derive benefit from (a
resource)" and nothing further.
> If you think it is not appropriate for PMBus devices to register as
> regulators, please let me know, and feel free to suggest a better
> solution.
My only intent was to observe the history of the problem highlighted by
Naresh's patch. I don't have any concerns about PMBus devices
registering as regulators.
Thanks,
Andrew
next prev parent reply other threads:[~2025-02-13 0:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 18:03 [PATCH 1/2] dt-bindings: hwmon: ir38060: Move & update dt binding Naresh Solanki
2025-02-04 18:03 ` [PATCH 2/2] ARM: dts: aspeed: sbp1: Update for ir38640 Naresh Solanki
2025-02-04 19:22 ` [PATCH 1/2] dt-bindings: hwmon: ir38060: Move & update dt binding Conor Dooley
2025-02-05 10:21 ` Naresh Solanki
2025-02-05 20:13 ` Conor Dooley
2025-02-06 15:53 ` Naresh Solanki
2025-02-06 18:09 ` Conor Dooley
2025-02-06 19:10 ` Naresh Solanki
2025-02-07 0:05 ` Conor Dooley
2025-02-12 10:43 ` Andrew Jeffery
2025-02-12 14:46 ` Guenter Roeck
2025-02-13 0:25 ` Andrew Jeffery [this message]
2025-02-12 18:56 ` Conor Dooley
2025-02-13 0:33 ` Andrew Jeffery
2025-02-04 23:34 ` Rob Herring (Arm)
-- strict thread matches above, loose matches on Subject: below --
2025-02-07 13:28 Naresh Solanki
2025-02-07 15:21 ` Rob Herring (Arm)
2025-02-12 17:57 ` Rob Herring
2025-02-12 18:33 ` Conor Dooley
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=27d51c2c498cc5921998829e5279bf136d10f2dc.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=naresh.solanki@9elements.com \
--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