From: Conor Dooley <conor@kernel.org>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: Lee Jones <lee@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Patrick Rudolph <patrick.rudolph@9elements.com>,
mazziesaccount@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mfd: Add regulator-compatible property
Date: Fri, 26 Jan 2024 16:20:18 +0000 [thread overview]
Message-ID: <20240126-deflate-ashy-158a91efb25a@spud> (raw)
In-Reply-To: <20240126114614.1424592-1-naresh.solanki@9elements.com>
[-- Attachment #1: Type: text/plain, Size: 2493 bytes --]
On Fri, Jan 26, 2024 at 05:16:14PM +0530, Naresh Solanki wrote:
> Add regulator-compatible property.
Why? I can see that this is what you did, but there's no justification
for it.
grepping for this property, the first thing I see is:
rg "regulator-compatible"
drivers/regulator/of_regulator.c
389: * based on either the deprecated property regulator-compatible if present,
428: "regulator-compatible", NULL);
486: name = of_get_property(child, "regulator-compatible", NULL);
The property is deprecated, so you'll need twice as good a justification
for adding it!
> Also update example.
>
> TEST=Run below command & make sure there is no error
> make DT_CHECKER_FLAGS=-m dt_binding_check
Same comment here as my other mail.
Thanks,
Conor.
>
> Signed-off-by: Naresh Solanki <naresh.solanki@9elements.com>
> ---
> Documentation/devicetree/bindings/mfd/maxim,max5970.yaml | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/maxim,max5970.yaml b/Documentation/devicetree/bindings/mfd/maxim,max5970.yaml
> index 0da5cae3852e..75175098cbc2 100644
> --- a/Documentation/devicetree/bindings/mfd/maxim,max5970.yaml
> +++ b/Documentation/devicetree/bindings/mfd/maxim,max5970.yaml
> @@ -74,6 +74,9 @@ properties:
> description: |
> The value of current sense resistor in microohms.
>
> + regulator-compatible:
> + pattern: "^SW[0-1]$"
> +
> required:
> - shunt-resistor-micro-ohms
>
> @@ -111,6 +114,8 @@ examples:
>
> regulators {
> sw0_ref_0: sw0 {
> + regulator-compatible = "SW0";
> + regulator-name = "p5v";
> shunt-resistor-micro-ohms = <12000>;
> };
> };
> @@ -145,9 +150,13 @@ examples:
>
> regulators {
> sw0_ref_1: sw0 {
> + regulator-compatible = "SW0";
> + regulator-name = "p5v_aux";
> shunt-resistor-micro-ohms = <12000>;
> };
> sw1_ref_1: sw1 {
> + regulator-compatible = "SW1";
> + regulator-name = "p3v3_aux";
> shunt-resistor-micro-ohms = <10000>;
> };
> };
>
> base-commit: ecb1b8288dc7ccbdcb3b9df005fa1c0e0c0388a7
> --
> 2.42.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-01-26 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 11:46 [PATCH] dt-bindings: mfd: Add regulator-compatible property Naresh Solanki
2024-01-26 16:20 ` Conor Dooley [this message]
2024-02-02 11:57 ` Naresh Solanki
2024-02-02 16:24 ` 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=20240126-deflate-ashy-158a91efb25a@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.com \
--cc=robh+dt@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