devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Saravanan Sekar <sravanhome@gmail.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, mark.rutland@arm.com,
	gregkh@linuxfoundation.org, Jonathan.Cameron@huawei.com,
	davem@davemloft.net, mchehab+samsung@kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: regulator: add document bindings for mp5416
Date: Mon, 3 Feb 2020 12:12:55 +0000	[thread overview]
Message-ID: <20200203121255.GA30513@bogus> (raw)
In-Reply-To: <20200122135958.13663-2-sravanhome@gmail.com>

On Wed, Jan 22, 2020 at 02:59:56PM +0100, Saravanan Sekar wrote:
> Add device tree binding information for mp5416 regulator driver.
> 
> Signed-off-by: Saravanan Sekar <sravanhome@gmail.com>
> ---
>  .../bindings/regulator/mps,mp5416.yaml        | 78 +++++++++++++++++++
>  1 file changed, 78 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/regulator/mps,mp5416.yaml
> 
> diff --git a/Documentation/devicetree/bindings/regulator/mps,mp5416.yaml b/Documentation/devicetree/bindings/regulator/mps,mp5416.yaml
> new file mode 100644
> index 000000000000..702508e4267f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/mps,mp5416.yaml
> @@ -0,0 +1,78 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/regulator/mps,mp5416.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Monolithic Power System MP5416 PMIC
> +
> +maintainers:
> +  - Saravanan Sekar <sravanhome@gmail.com>
> +
> +properties:
> +  $nodename:
> +    pattern: "pmic@[0-9a-f]{1,2}"

Needs a ^ and $.

> +  compatible:
> +    enum:
> +      - mps,mp5416
> +
> +  reg:
> +    maxItems: 1
> +
> +  regulators:
> +    type: object
> +    allOf:
> +      - $ref: regulator.yaml#

Does this node contain regulator properties?

> +    description: |
> +      list of regulators provided by this controller, must be named
> +      after their hardware counterparts BUCK[1-4] and LDO[1-4]
> +
> +    patternProperties:
> +      "^buck[1-4]$":
> +        $ref: "regulator.yaml#"

Must be under 'allOf' or other constraints are ignored.

> +        type: object
> +
> +      "^ldo[1-4]$":
> +        $ref: "regulator.yaml#"
> +        type: object
> +
> +    additionalProperties: false
> +  additionalProperties: false
> +
> +required:
> +  - compatible
> +  - reg
> +  - regulators
> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    i2c {
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        pmic@69 {
> +          compatible = "mps,mp5416";
> +          reg = <0x69>;
> +
> +          regulators {
> +
> +            buck1 {
> +             regulator-name = "buck1";
> +             regulator-min-microvolt = <600000>;
> +             regulator-max-microvolt = <2187500>;
> +             regulator-min-microamp  = <3800000>;
> +             regulator-max-microamp  = <6800000>;
> +             regulator-boot-on;
> +            };
> +
> +            ldo2 {
> +             regulator-name = "ldo2";
> +             regulator-min-microvolt = <800000>;
> +             regulator-max-microvolt = <3975000>;
> +            };
> +         };
> +       };
> +     };
> +...
> -- 
> 2.17.1
> 

  reply	other threads:[~2020-02-03 12:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 13:59 [PATCH 0/3] Add regulator support for mpq5416 Saravanan Sekar
2020-01-22 13:59 ` [PATCH 1/3] dt-bindings: regulator: add document bindings for mp5416 Saravanan Sekar
2020-02-03 12:12   ` Rob Herring [this message]
2020-01-22 13:59 ` [PATCH 2/3] regulator: mp5416: add mp5416 regulator driver Saravanan Sekar
2020-01-22 13:59 ` [PATCH 3/3] MAINTAINERS: Add entry for mp5416 PMIC driver Saravanan Sekar

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=20200203121255.GA30513@bogus \
    --to=robh@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=broonie@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mchehab+samsung@kernel.org \
    --cc=sravanhome@gmail.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;
as well as URLs for NNTP newsgroup(s).