linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh+dt@kernel.org>
To: Saravanan Sekar <sravanhome@gmail.com>, Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Maxime Ripard <mripard@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	"heiko@sntech.de" <heiko@sntech.de>,
	Sam Ravnborg <sam@ravnborg.org>, Icenowy Zheng <icenowy@aosc.io>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	David Miller <davem@davemloft.net>,
	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
	devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 2/4] dt-bindings: regulator: add document bindings for mpq7920
Date: Mon, 13 Jan 2020 10:56:55 -0600	[thread overview]
Message-ID: <CAL_JsqJ4vTzyfAG2UWzzkhVkBSLDRPjdyDUFZJ9LrDmsFsQ1gA@mail.gmail.com> (raw)
In-Reply-To: <20200109112548.23914-3-sravanhome@gmail.com>

On Thu, Jan 9, 2020 at 5:26 AM Saravanan Sekar <sravanhome@gmail.com> wrote:
>
> Add device tree binding information for mpq7920 regulator driver.
> Example bindings for mpq7920 are added.

Mark, Please revert this. Not even close to valid schema and my
questions on v4 are unanswered.

>
> Signed-off-by: Saravanan Sekar <sravanhome@gmail.com>
> ---
>  .../bindings/regulator/mps,mpq7920.yaml       | 202 ++++++++++++++++++
>  1 file changed, 202 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/regulator/mps,mpq7920.yaml
>
> diff --git a/Documentation/devicetree/bindings/regulator/mps,mpq7920.yaml b/Documentation/devicetree/bindings/regulator/mps,mpq7920.yaml
> new file mode 100644
> index 000000000000..598f3ea070c9
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/mps,mpq7920.yaml
> @@ -0,0 +1,202 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/regulator/mps,mpq7920.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Monolithic Power System MPQ7920 PMIC
> +
> +maintainers:
> +  - Saravanan Sekar <sravanhome@gmail.com>
> +
> +properties:
> +  $nodename:
> +    pattern: "pmic@[0-9a-f]{1,2}"
> +  compatible:
> +    enum:
> +      - mps,mpq7920
> +
> +  reg:
> +    maxItems: 1
> +
> +  regulators:
> +    type: object
> +    description: |
> +      list of regulators provided by this controller, must be named
> +      after their hardware counterparts BUCK[1-4], one LDORTC, and LDO[2-5]
> +
> +      mps,switch-freq:

This needs to be under 'properties'. Otherwise, everything below here
is just part of 'description'.

As I asked on v4, shouldn't this be a common property? Switching
frequency is a common property for switching regulators, right?

> +        description: |
> +          switching frequency must be one of following corresponding value
> +          1.1MHz, 1.65MHz, 2.2MHz, 2.75MHz
> +        $ref: "/schemas/types.yaml#/definitions/uint8"
> +        enum: [ 0, 1, 2, 3 ]
> +        default: 2
> +
> +      buck1:

This should be under 'patternProperties' as '^buck[1-4]$'. Then you
aren't duplicating a bunch of property schemas.

> +        type: object
> +        $ref: "regulator.yaml#"

Should be:

allOf:
  - $ref: regulator.yaml#

> +        description: |
> +          4.5A DC-DC step down converter
> +
> +        mps,buck-softstart:

Needs to be under 'properties'

> +           $ref: "/schemas/types.yaml#/definitions/uint8"
> +           enum: [ 0, 1, 2, 3 ]
> +           default: 1
> +           description: |
> +             defines the soft start time of this buck, must be one of the following
> +             corresponding values 150us, 300us, 610us, 920us
> +
> +         mps,buck-phase-delay:
> +           $ref: "/schemas/types.yaml#/definitions/uint8"
> +           enum: [ 0, 1, 2, 3 ]
> +           default: 0
> +           description: |
> +             defines the phase delay of this buck, must be one of the following
> +             corresponding values 0deg, 90deg, 180deg, 270deg
> +
> +         mps,buck-ovp-disable:
> +           type: boolean
> +           description: |
> +             disables over voltage protection of this buck

Seems like configurable over voltage protection would be a common
regulator property?

> +
> +      buck2:
> +        type: object
> +        $ref: "regulator.yaml#"
> +        description: |
> +          2.5A DC-DC step down converter
> +
> +        mps,buck-softstart:
> +          description: |
> +            defines the soft start time of this buck, must be one of the following
> +            corresponding values 150us, 300us, 610us, 920us
> +          $ref: "/schemas/types.yaml#/definitions/uint8"
> +          enum: [ 0, 1, 2, 3 ]
> +          default: 1
> +
> +        mps,buck-phase-delay:
> +          description: |
> +            defines the phase delay of this buck, must be one of the following
> +            corresponding values 0deg, 90deg, 180deg, 270deg
> +          $ref: "/schemas/types.yaml#/definitions/uint8"
> +          enum: [ 0, 1, 2, 3 ]
> +          default: 0
> +
> +        mps,buck-ovp-disable:
> +          description: |
> +            disables over voltage protection of this buck
> +          type: boolean
> +
> +      buck3:
> +        type: object
> +        $ref: "regulator.yaml#"
> +        description: |
> +          4.5A DC-DC step down converter
> +
> +        mps,buck-softstart:
> +           description: |
> +             defines the soft start time of this buck, must be one of the following
> +             corresponding values 150us, 300us, 610us, 920us
> +           $ref: "/schemas/types.yaml#/definitions/uint8"
> +           enum: [ 0, 1, 2, 3 ]
> +           default: 1
> +
> +         mps,buck-phase-delay:
> +           description: |
> +             defines the phase delay of this buck, must be one of the following
> +             corresponding values 0deg, 90deg, 180deg, 270deg
> +           $ref: "/schemas/types.yaml#/definitions/uint8"
> +           enum: [ 0, 1, 2, 3 ]
> +           default: 1
> +
> +         mps,buck-ovp-disable:
> +           description: |
> +             disables over voltage protection of this buck
> +           type: boolean
> +
> +      buck4:
> +        type: object
> +        $ref: "regulator.yaml#"
> +        description: |
> +          2.5A DC-DC step down converter
> +
> +        mps,buck-softstart:
> +          description: |
> +            defines the soft start time of this buck, must be one of the following
> +            corresponding values 150us, 300us, 610us, 920us
> +          $ref: "/schemas/types.yaml#/definitions/uint8"
> +          enum: [ 0, 1, 2, 3 ]
> +          default: 1
> +
> +        mps,buck-phase-delay:
> +          description: |
> +            defines the phase delay of this buck, must be one of the following
> +            corresponding values 0deg, 90deg, 180deg, 270deg
> +          $ref: "/schemas/types.yaml#/definitions/uint8"
> +          enum: [ 0, 1, 2, 3 ]
> +          default: 1
> +
> +        mps,buck-ovp-disable:
> +          description: |
> +            disables over voltage protection of this buck
> +          type: boolean
> +
> +      ldortc:

Again, make this a pattern.

> +        $ref: "regulator.yaml#"
> +        description: |
> +          regulator with 0.65V-3.5875V for RTC, always enabled
> +
> +      ldo2:
> +        $ref: "regulator.yaml#"
> +        description: |
> +          regulator with 0.65V-3.5875V
> +
> +      ldo3:
> +        $ref: "regulator.yaml#"
> +        description: |
> +          regulator with 0.65V-3.5875V
> +
> +      ldo4:
> +        $ref: "regulator.yaml#"
> +        description: |
> +          regulator with 0.65V-3.5875V
> +
> +      ldo5:
> +        $ref: "regulator.yaml#"
> +        description: |
> +          regulator with 0.65V-3.5875V

You need 'required' here listing compatible, reg, and regulators.

And then 'additionalProperties: false'

> +
> +examples:
> +  - |
> +    i2c {
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        pmic@69 {
> +          compatible = "mps,mpq7920";
> +          reg = <0x69>;
> +
> +          regulators {
> +            mps,switch-freq = <1>;
> +
> +            buck1 {
> +             regulator-name = "buck1";
> +             regulator-min-microvolt = <400000>;
> +             regulator-max-microvolt = <3587500>;
> +             regulator-min-microamp  = <460000>;
> +             regulator-max-microamp  = <7600000>;
> +             regulator-boot-on;
> +             mps,buck-ovp-disable;
> +             mps,buck-phase-delay = <2>;
> +             mps,buck-softstart = <1>;
> +            };
> +
> +            ldo2 {
> +             regulator-name = "ldo2";
> +             regulator-min-microvolt = <650000>;
> +             regulator-max-microvolt = <3587500>;
> +            };
> +         };
> +       };
> +     };
> +...
> --
> 2.17.1
>

  reply	other threads:[~2020-01-13 16:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09 11:25 [PATCH v6 0/4] Add regulator support for mpq7920 Saravanan Sekar
2020-01-09 11:25 ` [PATCH v6 1/4] dt-bindings: Add an entry for Monolithic Power System, MPS Saravanan Sekar
2020-01-13 17:14   ` Rob Herring
2020-01-14 11:53     ` Mark Brown
2020-01-09 11:25 ` [PATCH v6 2/4] dt-bindings: regulator: add document bindings for mpq7920 Saravanan Sekar
2020-01-13 16:56   ` Rob Herring [this message]
2020-01-14 12:33     ` Mark Brown
2020-01-09 11:25 ` [PATCH v6 3/4] regulator: mpq7920: add mpq7920 regulator driver Saravanan Sekar
2020-01-09 13:28   ` Mark Brown
2020-01-09 18:34     ` saravanan sekar
2020-01-09 19:16       ` Mark Brown
2020-01-09 11:25 ` [PATCH v6 4/4] MAINTAINERS: Add entry for mpq7920 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=CAL_JsqJ4vTzyfAG2UWzzkhVkBSLDRPjdyDUFZJ9LrDmsFsQ1gA@mail.gmail.com \
    --to=robh+dt@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=heiko@sntech.de \
    --cc=icenowy@aosc.io \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mchehab+samsung@kernel.org \
    --cc=mripard@kernel.org \
    --cc=sam@ravnborg.org \
    --cc=shawnguo@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).