Message ID | 20230418145051.4192963-1-Naresh.Solanki@9elements.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:b0ea:0:b0:3b6:4342:cba0 with SMTP id b10csp2912373vqo; Tue, 18 Apr 2023 07:54:18 -0700 (PDT) X-Google-Smtp-Source: AKy350ayz0imvAu7PXkykob/I3lUSmhLhMQx3NhuKWvb6RgsBsVxNmlkgyn1b8u3DrGeHt75G/v3 X-Received: by 2002:a05:6a20:9387:b0:ef:e017:c60f with SMTP id x7-20020a056a20938700b000efe017c60fmr8962882pzh.51.1681829658561; Tue, 18 Apr 2023 07:54:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681829658; cv=none; d=google.com; s=arc-20160816; b=EhZ+YaWtPInjDm3fNTd/cOyql78Ley5sD1gMbo7OBElc7sIYqwGJxgXugFuQ+Dgmig CVIv0MaZLbm7uyKWRKut4ZxyZ5eD7HkLtBPDr7iPQdKkYTNyo/XEaZtjxW8svR+159Zk 2KxXcm8liNElEHVy9cuDDy1NxLjic94b4xsIlVRSKQTz1Z/1nvG3xAovhwkqu3nQrtRY 8evot9IHZr/k4wP8hID1EzYxNrIOQXo30IBPwcmDcbeqQtaPXCRr22YSW4mV9n/Em98T nxU/uWNNe7RhUJeTIPS8G1Hcz9v7fXrWUb/LlYbpbsMP1kAv7uZutXU8y5OIFwZwZd6U lDPw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=kIM8LW6yI6V143LdhT1FdSGC5xNGvUqWMyNhdIh0gqk=; b=leYvnruofQ/C3OGdlknPSu4xhvE0JhGZN8fObP8YO1OVp/UqhvqK78HT54DQIVfuIJ QV7/eMQwDXAA6+QJXTEnSAHg1U1+2tsJDD9uPqOFQIeSbXj5UsTc+CQE2TtScDyFp0gx 41VIIKJMkhEqp8rSHHS+gO9KHyADK8I/zWUDqAGjNRiY8573b3doHBtTd7IQWO7dcLGs /mtuOHODf48cAHBKvBVJCRvsd2YwskGozvIexiSXTeVF9u9Lq5PnemdceeaQUvEMZVRe jtIPAYtOYekP0PWpESTLE7haWXgK2dq9gWRtdkhbpaCGDUw4BC+aPSsovxy768pC4Gvy jcng== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@9elements.com header.s=google header.b=ciG0U0QR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=9elements.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b18-20020a63eb52000000b00513f15fe82dsi15023999pgk.786.2023.04.18.07.54.03; Tue, 18 Apr 2023 07:54:18 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@9elements.com header.s=google header.b=ciG0U0QR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=9elements.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231701AbjDROvL (ORCPT <rfc822;leviz.kernel.dev@gmail.com> + 99 others); Tue, 18 Apr 2023 10:51:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47446 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231485AbjDROu7 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Tue, 18 Apr 2023 10:50:59 -0400 Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 94850B77B for <linux-kernel@vger.kernel.org>; Tue, 18 Apr 2023 07:50:58 -0700 (PDT) Received: by mail-wm1-x333.google.com with SMTP id 5b1f17b1804b1-3f09b9ac51dso69945775e9.0 for <linux-kernel@vger.kernel.org>; Tue, 18 Apr 2023 07:50:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=9elements.com; s=google; t=1681829457; x=1684421457; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=kIM8LW6yI6V143LdhT1FdSGC5xNGvUqWMyNhdIh0gqk=; b=ciG0U0QRb/NtYe41cCi/q6OdFth5UhsN/iDd2EGKEg6ZiIMqhZOrtWTKm4RzjQ7V4x SG6tPhxsMBoSPyg/USw2sFeZX47bslwOoMGthdyWnTrxhINAm1Sx09QYoEU0j8FQqj3m w9x2HmKD97bO91i2W8MbRHmEOMPKXlqiafPsO62wWViGAoof8j+vvGIxqY+eoceb9RiR fAlY0EpLzv8fYDgH/UEAXCo6XElzwjMOI69zF0v0EaMYPcu2kffTndwIIvfUbzT+eiU5 Ss1BfG0RuANMUIHkDV8gkfDGi18LYQW5TrbVBBOEQp6eC+0McS70skcwRRla1ybCEkpV Nirw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681829457; x=1684421457; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=kIM8LW6yI6V143LdhT1FdSGC5xNGvUqWMyNhdIh0gqk=; b=JIGVJJYheHzVC2Yo/jJfzpVXsdsyw+wh0UD7h0XaOxAWLzkTPudGL7dvk6wCFEk20x vNuSd6FSmP2siB1SQkUhJet9ADoRNafdGJaErQmvq9udMJcxNk2RAcJHk1HoCiFV9qxY dF3gB9Ehp/WpC8hAQJy6CD2vYinL6psuTBuK1lmpMl+PdiMD9mDTJEDbIMs9ud9D4QGF 9OhVDOF/FmNwYzHWaEWdLjNiaVsTjjkgoItI4NaQNsLCX6o6Z5YzDkBBVvaSBVuIRZpB FEmx37ToPrhnCU+we2NAeo3aq4LL2uusPFE8HegmChpMnU51sx8WU+vtW3klEFXOC2jA 1S5w== X-Gm-Message-State: AAQBX9eZ0LQSHUcexsVlg3/61f93Ws2X8HP9MA+m0vzYj7BeUDhtjhW+ lXS4ugIgoiF0gQYtUI/PtSjv6Q== X-Received: by 2002:adf:dfc3:0:b0:2fb:b869:bc08 with SMTP id q3-20020adfdfc3000000b002fbb869bc08mr2181140wrn.23.1681829457063; Tue, 18 Apr 2023 07:50:57 -0700 (PDT) Received: from stroh80.sec.9e.network (ip-078-094-000-051.um19.pools.vodafone-ip.de. [78.94.0.51]) by smtp.gmail.com with ESMTPSA id z16-20020adff750000000b002fb6a79dea0sm3787823wrp.7.2023.04.18.07.50.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 18 Apr 2023 07:50:56 -0700 (PDT) From: Naresh Solanki <naresh.solanki@9elements.com> X-Google-Original-From: Naresh Solanki <Naresh.Solanki@9elements.com> To: Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Zev Weiss <zev@bewilderbeest.net> Cc: Naresh Solanki <Naresh.Solanki@9elements.com>, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Subject: [PATCH 1/2] dt-bindings: regulator: Add dt property Date: Tue, 18 Apr 2023 16:50:50 +0200 Message-Id: <20230418145051.4192963-1-Naresh.Solanki@9elements.com> X-Mailer: git-send-email 2.39.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1763526215905573299?= X-GMAIL-MSGID: =?utf-8?q?1763526215905573299?= |
Series |
[1/2] dt-bindings: regulator: Add dt property
|
|
Commit Message
Naresh Solanki
April 18, 2023, 2:50 p.m. UTC
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(-)
base-commit: c55470f8b0616b0adb758077dbae9b19c5aac005
Comments
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? >+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. A slightly more descriptive subject line would also be good -- "Add dt property" is a bit vague. >base-commit: c55470f8b0616b0adb758077dbae9b19c5aac005 >-- >2.39.1 >
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. > >> +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' > >> base-commit: c55470f8b0616b0adb758077dbae9b19c5aac005 >> -- >> 2.39.1 >> Regards, Naresh
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
Hi Zev, On 20-04-2023 04:11 pm, Zev Weiss wrote: > 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 Ack > >>> >>>> +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. Thanks :) > >>> >>>> base-commit: c55470f8b0616b0adb758077dbae9b19c5aac005 >>>> -- >>>> 2.39.1 >>>> >> Regards, >> Naresh Regards, Naresh
On Thu, Apr 20, 2023 at 01:52:30PM +0530, 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. > > > > > +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' And indicate this is for regulator-output, As-is looks like it's something for all regulators. Rob
Hi Rob, On 21-04-2023 11:40 pm, Rob Herring wrote: > On Thu, Apr 20, 2023 at 01:52:30PM +0530, 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. >>> >>>> +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' > > And indicate this is for regulator-output, As-is looks like it's > something for all regulators. Thanks for bringing that to my notice. Will make: dt-bindings: regulator-output: Add dt property > > Rob Regards, Naresh
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" + +patternProperties: + ".*-supply": + description: + Specified the phandle for various supplies required: - compatible - - vout-supply additionalProperties: false