From: Rob Herring <robh@kernel.org>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: broonie@kernel.org, zev@bewilderbeest.net,
Liam Girdwood <lgirdwood@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: regulator: regulator-output: Multiple supplies
Date: Wed, 4 Oct 2023 10:14:33 -0500 [thread overview]
Message-ID: <20231004151433.GA3145438-robh@kernel.org> (raw)
In-Reply-To: <20231004120529.1155700-1-naresh.solanki@9elements.com>
On Wed, Oct 04, 2023 at 02:05:26PM +0200, Naresh Solanki wrote:
> Add support for multiple supplies.
Why?
>
> Signed-off-by: Naresh Solanki <naresh.solanki@9elements.com>
> ---
> .../devicetree/bindings/regulator/regulator-output.yaml | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/regulator/regulator-output.yaml b/Documentation/devicetree/bindings/regulator/regulator-output.yaml
> index 078b37a1a71a..6d077f123729 100644
> --- a/Documentation/devicetree/bindings/regulator/regulator-output.yaml
> +++ b/Documentation/devicetree/bindings/regulator/regulator-output.yaml
> @@ -21,13 +21,13 @@ properties:
> compatible:
> const: regulator-output
>
> - vout-supply:
> +patternProperties:
> + ".*-supply":
> description:
> Phandle of the regulator supplying the output.
>
> required:
> - compatible
> - - vout-supply
>
> additionalProperties: false
>
> @@ -37,3 +37,8 @@ examples:
> compatible = "regulator-output";
> vout-supply = <&output_reg>;
> };
> + output1 {
> + compatible = "regulator-output";
> + sw0-supply = <&output_reg0>;
> + sw1-supply = <&output_reg2>;
> + };
>
> base-commit: f9a1d31874c383f58bb4f89bfe79b764682cd026
> --
> 2.41.0
>
next prev parent reply other threads:[~2023-10-04 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 12:05 [PATCH 1/3] dt-bindings: regulator: regulator-output: Multiple supplies Naresh Solanki
2023-10-04 15:14 ` Rob Herring [this message]
2023-10-05 7:46 ` Naresh Solanki
2023-10-05 8:41 ` Krzysztof Kozlowski
2023-10-05 11:17 ` Zev Weiss
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=20231004151433.GA3145438-robh@kernel.org \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@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=zev@bewilderbeest.net \
/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;
as well as URLs for NNTP newsgroup(s).