From: Zev Weiss <zev@bewilderbeest.net>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: regulator: Add dt property
Date: Thu, 20 Apr 2023 03:41:30 -0700 [thread overview]
Message-ID: <048bf9f4-92ee-4aca-a46f-dbe512129ffe@hatter.bewilderbeest.net> (raw)
In-Reply-To: <9f425205-c395-648a-3f42-a776c7580a8f@9elements.com>
On Thu, Apr 20, 2023 at 01:22:30AM PDT, Naresh Solanki wrote:
>Hi Zev,
>
>On 20-04-2023 05:31 am, Zev Weiss wrote:
>>On Tue, Apr 18, 2023 at 07:50:50AM PDT, Naresh Solanki wrote:
>>>Add DT property regulator-supplies.
>>>This enables us to couple one or more regulator output to gether. This
>>>is use in case of Single connector having 2 or more supplies.
>>>
>>>Signed-off-by: Naresh Solanki <Naresh.Solanki@9elements.com>
>>>---
>>>.../bindings/regulator/regulator-output.yaml | 12 +++++++++---
>>>1 file changed, 9 insertions(+), 3 deletions(-)
>>>
>>>diff --git
>>>a/Documentation/devicetree/bindings/regulator/regulator-output.yaml
>>>b/Documentation/devicetree/bindings/regulator/regulator-output.yaml
>>>index 078b37a1a71a..17f683d3c1f3 100644
>>>--- a/Documentation/devicetree/bindings/regulator/regulator-output.yaml
>>>+++ b/Documentation/devicetree/bindings/regulator/regulator-output.yaml
>>>@@ -21,13 +21,19 @@ properties:
>>> compatible:
>>> const: regulator-output
>>>
>>>- vout-supply:
>>>+ regulator-supplies:
>>> description:
>>>- Phandle of the regulator supplying the output.
>>>+ Specifies the name of the output supply provided by the regulator.
>>>+ Defaults to "vout".
>>>+ default: "vout"
>>>+
>>
>>Was this meant to be specified as a string-array to allow providing
>>multiple names?
>Yes. This is string-array.
Okay -- in that case I think it should include
$ref: /schemas/types.yaml#/definitions/string-array
>>
>>>+patternProperties:
>>>+ ".*-supply":
>>>+ description:
>>>+ Specified the phandle for various supplies
>>>
>>>required:
>>> - compatible
>>>- - vout-supply
>>>
>>>additionalProperties: false
>>>
>>>
>>
>>I think it would be nice to also update the examples to show what a
>>multi-supply instance would look like.
>Ack. Will do that.
>>
>>A slightly more descriptive subject line would also be good -- "Add
>>dt property" is a bit vague.
>Suggestion ?
>How about like 'Allow multiple supplies' or 'Add support for multiple
>supplies'
Sure, both of those sound fine to me.
>>
>>>base-commit: c55470f8b0616b0adb758077dbae9b19c5aac005
>>>--
>>>2.39.1
>>>
>Regards,
>Naresh
next prev parent reply other threads:[~2023-04-20 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 14:50 Naresh Solanki
2023-04-18 14:50 ` [PATCH 2/2] regulator: userspace-consumer: Multiple regulators Naresh Solanki
2023-04-20 0:02 ` Zev Weiss
2023-04-20 8:46 ` Naresh Solanki
2023-04-20 10:57 ` Zev Weiss
2023-04-20 12:27 ` Naresh Solanki
2023-04-20 0:01 ` [PATCH 1/2] dt-bindings: regulator: Add dt property Zev Weiss
2023-04-20 8:22 ` Naresh Solanki
2023-04-20 10:41 ` Zev Weiss [this message]
2023-04-20 11:32 ` Naresh Solanki
2023-04-21 18:10 ` Rob Herring
2023-04-24 7:49 ` Naresh Solanki
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=048bf9f4-92ee-4aca-a46f-dbe512129ffe@hatter.bewilderbeest.net \
--to=zev@bewilderbeest.net \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@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
all inboxes | Powered by JetHome®