public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Luca Ceresoli <luca@lucaceresoli.net>
Cc: Lee Jones <lee.jones@linaro.org>, Keerthy <j-keerthy@ti.com>,
	Axel Lin <axel.lin@ingics.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/3] dt-bindings: mfd: add LP87524-Q1
Date: Tue, 25 Aug 2020 13:15:10 -0600	[thread overview]
Message-ID: <20200825191510.GA1152696@bogus> (raw)
In-Reply-To: <20200817145018.3992-3-luca@lucaceresoli.net>

On Mon, Aug 17, 2020 at 04:50:17PM +0200, Luca Ceresoli wrote:
> Add the LP87524-Q1 to the bindings along with an example. This is a variant
> of the LP87565-Q1 and LP87561-Q1 chips which already have bindings.
> 
> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
> 
> ---
> 
> Changes in v4:
>  - reformat as a standalone file
> 
> Changes in v3:
>  - fix yaml errors
> 
> Changes in v2:
>  - RFC,v1 was based on the txt file, rewrite for yaml
>  - use uppercase consistently in model names (Lee Jones)
>  - replace "regulator" -> "mfd" in subject line (Lee Jones)
>  - replace "dt:" suffix with "dt-bindings:" prefix in subject line
> ---
>  .../bindings/mfd/ti,lp87524-q1.yaml           | 105 ++++++++++++++++++
>  1 file changed, 105 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/mfd/ti,lp87524-q1.yaml
> 
> diff --git a/Documentation/devicetree/bindings/mfd/ti,lp87524-q1.yaml b/Documentation/devicetree/bindings/mfd/ti,lp87524-q1.yaml
> new file mode 100644
> index 000000000000..1193fcb19739
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/ti,lp87524-q1.yaml
> @@ -0,0 +1,105 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mfd/ti,lp87524-q1.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: TI LP87524-Q1 four 1-phase output buck converter
> +
> +maintainers:
> +  - Keerthy <j-keerthy@ti.com>
> +
> +properties:
> +  compatible:
> +    const: ti,lp87524-q1
> +
> +  reg:
> +    description: I2C slave address
> +    const: 0x60
> +
> +  gpio-controller: true
> +
> +  '#gpio-cells':
> +    description:
> +      The first cell is the pin number.
> +      The second cell is is used to specify flags.
> +      See ../gpio/gpio.txt for more information.
> +    const: 2
> +
> +  buck0-in-supply:
> +    description:
> +      Phandle to parent supply node for the BUCK0 converter.
> +
> +  buck1-in-supply:
> +    description:
> +      Phandle to parent supply node for the BUCK1 converter.
> +
> +  buck2-in-supply:
> +    description:
> +      Phandle to parent supply node for the BUCK2 converter.
> +
> +  buck3-in-supply:
> +    description:
> +      Phandle to parent supply node for the BUCK3 converter.
> +
> +required:
> +  - compatible
> +  - reg
> +  - gpio-controller
> +  - '#gpio-cells'
> +  - buck0-in-supply
> +  - buck1-in-supply
> +  - buck2-in-supply
> +  - buck3-in-supply
> +
> +examples:
> +  - |
> +    i2c@0 {
> +        reg = <0x0 0x100>;
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        pmic@60 {
> +            compatible = "ti,lp87524-q1";
> +            reg = <0x60>;
> +            gpio-controller;
> +            #gpio-cells = <2>;
> +
> +            buck0-in-supply = <&vdd_5v0>;
> +            buck1-in-supply = <&vdd_5v0>;
> +            buck2-in-supply = <&vdd_5v0>;
> +            buck3-in-supply = <&vdd_5v0>;
> +
> +            regulators {
> +                buck0_reg: buck0 {

Here too, you need to describe all this.

> +                    regulator-name = "buck0";
> +                    regulator-min-microvolt = <3300000>;
> +                    regulator-max-microvolt = <3300000>;
> +                    regulator-always-on;
> +                };
> +
> +                buck1_reg: buck1 {
> +                    regulator-name = "buck1";
> +                    regulator-min-microvolt = <1350000>;
> +                    regulator-max-microvolt = <1350000>;
> +                    regulator-always-on;
> +                };
> +
> +                buck2_reg: buck2 {
> +                    regulator-name = "buck2";
> +                    regulator-min-microvolt = <950000>;
> +                    regulator-max-microvolt = <950000>;
> +                    regulator-always-on;
> +                };
> +
> +                buck3_reg: buck3 {
> +                    regulator-name = "buck3";
> +                    regulator-min-microvolt = <1800000>;
> +                    regulator-max-microvolt = <1800000>;
> +                    regulator-always-on;
> +                };
> +            };
> +        };
> +    };
> +
> +...
> -- 
> 2.28.0
> 

  reply	other threads:[~2020-08-25 19:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17 14:50 [PATCH v4 0/3] mfd: lp87565: convert DT to yaml and add LP87524-Q1 Luca Ceresoli
2020-08-17 14:50 ` [PATCH v4 1/3] dt-bindings: mfd: lp87565: convert to yaml Luca Ceresoli
2020-08-25 19:14   ` Rob Herring
2020-08-17 14:50 ` [PATCH v4 2/3] dt-bindings: mfd: add LP87524-Q1 Luca Ceresoli
2020-08-25 19:15   ` Rob Herring [this message]
2020-08-17 14:50 ` [PATCH v4 3/3] mfd: lp87565: add LP87524-Q1 variant Luca Ceresoli

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=20200825191510.GA1152696@bogus \
    --to=robh@kernel.org \
    --cc=axel.lin@ingics.com \
    --cc=devicetree@vger.kernel.org \
    --cc=j-keerthy@ti.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca@lucaceresoli.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