public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Patrick Rudolph <patrick.rudolph@9elements.com>
Subject: Re: [PATCH v4 2/4] dt-bindings: regulator: add bindings for output-supply
Date: Thu, 14 Jul 2022 08:10:41 -0600	[thread overview]
Message-ID: <20220714141041.GB2229197-robh@kernel.org> (raw)
In-Reply-To: <20220707081826.953449-3-Naresh.Solanki@9elements.com>

On Thu, Jul 07, 2022 at 10:18:24AM +0200, Naresh Solanki wrote:
> Add a devicetree binding for the 9elements,output-supply driver.

Bindings are for h/w, not drivers.

> Example is also provided.
> 
> Signed-off-by: Naresh Solanki <Naresh.Solanki@9elements.com>
> ---
>  .../regulator/9elements,output-supply.yaml    | 63 +++++++++++++++++++
>  1 file changed, 63 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/regulator/9elements,output-supply.yaml
> 
> diff --git a/Documentation/devicetree/bindings/regulator/9elements,output-supply.yaml b/Documentation/devicetree/bindings/regulator/9elements,output-supply.yaml
> new file mode 100644
> index 000000000000..e4b67bc0794f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/9elements,output-supply.yaml
> @@ -0,0 +1,63 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/regulator/userspace-consumer.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Regulator output-supply driver
> +
> +maintainers:
> +  - Patrick Rudolph <patrick.rudolph@9elements.com>
> +
> +description: |
> +  Regulator output-supply driver helps interact with regulator.
> +  Provides regulator events & sysfs notify to capture regulator events
> +  in realtime for userspace application.
> +  This enables userspace application to monitor events in regulator(s) &
> +  handle them appropriately.

What does userspace have to do with hardware description?

> +
> +
> +properties:
> +  compatible:
> +    enum:
> +      - 9elements,output-supply

Why does this have a vendor prefix when it appears to be a s/w 
construct?

> +
> +  regulator-name:
> +    description: Name of the consumer line
> +
> +  regulator-boot-on:
> +    description: Enable regulator during boot
> +
> +  regulator-supplies:
> +    description: Supply names for this regulator. This can be multiple strings

What's the type for this? 

The supply names are the prefix on -supply properties.

> +
> +patternProperties:
> +  ".*-supply$":
> +    description: |
> +      Input supply phandle(s) for this node. There should be
> +      <supply-name>-supply to pass regulators handle
> +
> +required:
> +  - compatible
> +  - regulator-supplies
> +  - ".*-supply$"
> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    p12v_b_consumer {
> +        compatible = "9elements,output-supply";
> +        regulator-name = "BCM1";
> +        regulator-supplies = "vbus";
> +        vbus-supply = <&p12v_b>;
> +    };
> +
> +    ssb_rssd32 {
> +        compatible = "9elements,output-supply";
> +        regulator-name = "ssb_rssd32";
> +        regulator-supplies = "sw0", "sw1";
> +        sw0-supply = <&sw0_ssb_rssd32>;
> +        sw1-supply = <&sw1_ssb_rssd32>;
> +    };
> +...
> -- 
> 2.35.3
> 
> 

  parent reply	other threads:[~2022-07-14 14:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07  8:18 [PATCH v4 0/4] regulator: output-supply DT support Naresh Solanki
2022-07-07  8:18 ` [PATCH v4 1/4] dt-bindings: vendor-prefixes: add 9elements Naresh Solanki
2022-07-11 22:19   ` Rob Herring
2022-07-07  8:18 ` [PATCH v4 2/4] dt-bindings: regulator: add bindings for output-supply Naresh Solanki
2022-07-08 18:33   ` Mark Brown
2022-07-14 14:02   ` Rob Herring
2022-07-14 14:10   ` Rob Herring [this message]
2022-07-14 14:14     ` Mark Brown
2022-07-14 14:23       ` Rob Herring
2022-07-14 14:42         ` Mark Brown
2022-07-14 15:07           ` Rob Herring
2022-07-14 15:54             ` Mark Brown
2022-07-14 16:59               ` Rob Herring
2022-07-14 17:50                 ` Mark Brown
2022-07-21  8:33                 ` Zev Weiss
2022-07-21 11:05                   ` Mark Brown
2022-07-07  8:18 ` [PATCH v4 3/4] regulator: output-supply: Add devicetree support Naresh Solanki
2022-07-07  8:18 ` [PATCH v4 4/4] regulator: output-supply: Add Notification support Naresh Solanki
2022-07-11 19:11 ` [PATCH v4 0/4] regulator: output-supply DT support Mark Brown
2022-07-14 14:17   ` Rob Herring
2022-07-14 18:24     ` Mark Brown

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=20220714141041.GB2229197-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naresh.solanki@9elements.com \
    --cc=patrick.rudolph@9elements.com \
    /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