Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>,
	Hardware Monitoring <linux-hwmon@vger.kernel.org>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
	Cedricjustine.Encarnacion@analog.com
Subject: Re: [PATCH RFT/RFC] hwmon: (pmbus) Do not set regulators_node for single-channel chips
Date: Sat, 22 Mar 2025 17:46:30 +0100	[thread overview]
Message-ID: <50a025ef-d9ca-469e-bb42-e5dcefc84570@kernel.org> (raw)
In-Reply-To: <20250322142602.560042-1-linux@roeck-us.net>

On 22/03/2025 15:26, Guenter Roeck wrote:
> Single-channel regulators do not need and should not have a "regulators"
> node. We can not entirely remove it due to existing bindings. To solve the
> problem for new drivers, provide additional macros PMBUS_REGULATOR_ONE_NODE
> and PMBUS_REGULATOR_STEP_ONE_NODE and convert existing drivers to use those
> macros. The exception is the ir38064 driver because its devicetree files
> and its description do not require or use the nested regulators node.
> 
> Modify PMBUS_REGULATOR_STEP_ONE and PMBUS_REGULATOR_ONE to set the
> regulators_node pointer to NULL.
> 
> Cc: Cedricjustine.Encarnacion@analog.com
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
> RFT: Untested. Open question is if not setting .regulators_node is
>      sufficient to solve the problem.
> RFC: Open question is if existing bindings (if unused in-tree) should
>      be converted to not require the nested "regulators" node.

Looks correct.


Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Best regards,
Krzysztof

  reply	other threads:[~2025-03-22 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-22 14:26 [PATCH RFT/RFC] hwmon: (pmbus) Do not set regulators_node for single-channel chips Guenter Roeck
2025-03-22 16:46 ` Krzysztof Kozlowski [this message]
2025-04-07 22:50 ` 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=50a025ef-d9ca-469e-bb42-e5dcefc84570@kernel.org \
    --to=krzk@kernel.org \
    --cc=Cedricjustine.Encarnacion@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=linux-hwmon@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