devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Georgi Vlaev <g-vlaev@ti.com>, devicetree@vger.kernel.org
Cc: robh+dt@kernel.org, lgirdwood@gmail.com, broonie@kernel.org,
	ldewangan@nvidia.com, nm@ti.com, vigneshr@ti.com
Subject: Re: [PATCH] dt-bindings: regulator: Convert TPS62360 binding to json-schema
Date: Thu, 3 Mar 2022 18:47:20 +0100	[thread overview]
Message-ID: <54caddff-a944-93c2-aaed-ffe80e83018e@canonical.com> (raw)
In-Reply-To: <20220303120017.30181-1-g-vlaev@ti.com>

On 03/03/2022 13:00, Georgi Vlaev wrote:
> Convert the TPS62360 regulator binding to DT schema format
> using json-schema.
> 
> Signed-off-by: Georgi Vlaev <g-vlaev@ti.com>
> ---
>  .../bindings/regulator/ti,tps62360.yaml       | 99 +++++++++++++++++++
>  .../bindings/regulator/tps62360-regulator.txt | 44 ---------
>  2 files changed, 99 insertions(+), 44 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/regulator/ti,tps62360.yaml
>  delete mode 100644 Documentation/devicetree/bindings/regulator/tps62360-regulator.txt
> 
> diff --git a/Documentation/devicetree/bindings/regulator/ti,tps62360.yaml b/Documentation/devicetree/bindings/regulator/ti,tps62360.yaml
> new file mode 100644
> index 000000000000..73674ef4d903
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/ti,tps62360.yaml
> @@ -0,0 +1,99 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/regulator/ti,tps62360.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Texas Instruments TPS6236x Voltage Regulators
> +
> +maintainers:
> +  - Laxman Dewangan <ldewangan@nvidia.com>
> +
> +description: |
> +  The TPS6236x are a family of step down dc-dc converter with
> +  an input voltage range of 2.5V to 5.5V. The devices provide
> +  up to 3A peak load current, and an output voltage range of
> +  0.77V to 1.4V (TPS62360/62) and 0.5V to 1.77V (TPS62361B/63).
> +
> +  Datasheet is available at:
> +  https://www.ti.com/lit/gpn/tps62360
> +
> +allOf:
> +  - $ref: "regulator.yaml#"
> +
> +properties:
> +  compatible:
> +    enum:
> +      - ti,tps62360
> +      - ti,tps62361
> +      - ti,tps62362
> +      - ti,tps62363
> +
> +  reg:
> +    maxItems: 1
> +
> +  ti,vsel0-gpio:
> +    description: |
> +      GPIO for controlling VSEL0 line. If this property
> +      is missing, then assume that there is no GPIO for
> +      VSEL0 control.
> +    maxItems: 1
> +
> +  ti,vsel1-gpio:
> +    description: |
> +      GPIO for controlling VSEL1 line. If this property
> +      is missing, then assume that there is no GPIO for
> +      VSEL1 control.
> +    maxItems: 1
> +
> +  ti,enable-vout-discharge:
> +    description: Enable output discharge.
> +    type: boolean
> +
> +  ti,enable-pull-down:
> +    description: Enable pull down.
> +    type: boolean
> +
> +  ti,vsel0-state-high:
> +    description: |
> +      Initial state of VSEL0 input is high. If this property
> +      is missing, then assume the state as low.
> +    type: boolean
> +
> +  ti,vsel1-state-high:
> +    description: |
> +      Initial state of VSEL1 input is high. If this property
> +      is missing, then assume the state as low.
> +    type: boolean
> +
> +required:
> +  - compatible
> +  - reg
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    #include <dt-bindings/gpio/gpio.h>
> +    i2c {
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        regulator@60 {
> +          compatible = "ti,tps62361";

In-consisting indentation. Use 4 spaces for entire DT example.

Rest looks good.



Best regards,
Krzysztof

  reply	other threads:[~2022-03-03 17:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 12:00 [PATCH] dt-bindings: regulator: Convert TPS62360 binding to json-schema Georgi Vlaev
2022-03-03 17:47 ` Krzysztof Kozlowski [this message]
2022-03-04  8:08   ` [PATCH v2] " Georgi Vlaev
2022-03-04  8:11     ` Krzysztof Kozlowski
2022-03-04  8:41       ` Laxman Dewangan
2022-03-07 12:37     ` 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=54caddff-a944-93c2-aaed-ffe80e83018e@canonical.com \
    --to=krzysztof.kozlowski@canonical.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=g-vlaev@ti.com \
    --cc=ldewangan@nvidia.com \
    --cc=lgirdwood@gmail.com \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.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).