linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: cy_huang <u0084500@gmail.com>,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	lee.jones@linaro.org, broonie@kernel.org,
	dmitry.torokhov@gmail.com
Cc: lgirdwood@gmail.com, cy_huang@richtek.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-input@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-binding: mfd: Add Richtek RT5120 PMIC support
Date: Tue, 7 Jun 2022 13:52:56 +0200	[thread overview]
Message-ID: <96ecca0b-b65c-749d-d66b-33443cacf2e4@linaro.org> (raw)
In-Reply-To: <1654581161-12349-2-git-send-email-u0084500@gmail.com>

On 07/06/2022 07:52, cy_huang wrote:
> From: ChiYuan Huang <cy_huang@richtek.com>
> 
> Add Richtek RT5120 PMIC devicetree document.
> 
> Signed-off-by: ChiYuan Huang <cy_huang@richtek.com>
> ---
>  .../devicetree/bindings/mfd/richtek,rt5120.yaml    | 180 +++++++++++++++++++++
>  1 file changed, 180 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/mfd/richtek,rt5120.yaml
> 
> diff --git a/Documentation/devicetree/bindings/mfd/richtek,rt5120.yaml b/Documentation/devicetree/bindings/mfd/richtek,rt5120.yaml
> new file mode 100644
> index 00000000..376bf73
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/richtek,rt5120.yaml
> @@ -0,0 +1,180 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mfd/richtek,rt5120.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Richtek RT5120 PMIC
> +
> +maintainers:
> +  - ChiYuan Huang <cy_huang@richtek.com>
> +
> +description: |
> +  The RT5120 provides four high-efficiency buck converters and one LDO voltage
> +  regulator. The device is targeted at providingthe processor voltage, memory,
> +  I/O, and peripheral rails in home entertainment devices. The I2C interface is
> +  used for dynamic voltage scaling of the processor voltage, power rails on/off
> +  sequence control, operation mode selection.
> +
> +properties:
> +  compatible:
> +    enum:
> +      - richtek,rt5120
> +
> +  reg:
> +    maxItems: 1
> +
> +  interrupts:
> +    maxItems: 1
> +
> +  interrupt-controller: true
> +
> +  "#interrupt-cells":
> +    const: 1
> +
> +  wakeup-source: true
> +
> +  richtek,enable-undervolt-hiccup:
> +    type: boolean
> +    description: |
> +      If used, under voltage protection trigger hiccup behavior, else latchup as
> +      default
> +
> +  richtek,enable-overvolt-hiccup:
> +    type: boolean
> +    description:
> +      Like as 'enable-uv-hiccup', it configures over voltage protection to
> +      hiccup, else latchup as default
> +
> +  vin1-supply:
> +    description: phandle for buck1 input power source
> +
> +  vin2-supply:
> +    description: phandle for buck2 input power source
> +
> +  vin3-supply:
> +    description: phandle for buck3 input power source
> +
> +  vin4-supply:
> +    description: phandle for buck4 input power source
> +
> +  vinldo-supply:
> +    description: phandle for ldo input power source
> +
> +  regulators:
> +    type: object
> +
> +    patternProperties:
> +      "^buck[1-4]$":
> +        type: object
> +        $ref: /schemas/regulator/regulator.yaml#
> +
> +        properties:
> +          regulator-allowed-modes:
> +            description: |
> +              Used to specify the allowed buck converter operating mode
> +              mode mapping:
> +                0: auto mode
> +                1: force pwm mode
> +            items:
> +              enum: [0, 1]
> +
> +        unevaluatedProperties: false

Better to put it after '$ref' for readability.

> +
> +      "^(ldo|exten)$":
> +        type: object
> +        $ref: /schemas/regulator/regulator.yaml#

You need here unevaluatedProperties:false as well (for the ldo/exten
properties)

> +
> +    additionalProperties: false
> +
> +  powerkey:
> +    type: object
> +    description:
> +      The power key driver may be optional. If not used, change node status to
> +      'disabled'

This description is not helpful, does not describe the hardware. Please
describe hardware, not Devicetree usage.

> +
> +    properties:
> +      compatible:
> +        enum:
> +          - richtek,rt5120-pwrkey
> +
> +    required:
> +      - compatible
> +
> +    additionalProperties: false
> +
> +required:
> +  - compatible
> +  - reg
> +  - interrupts
> +  - '#interrupt-cells'
> +  - interrupt-controller
> +  - regulators
> +  - powerkey

You wrote powerkey is optional... so the node should not be required, right?

> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    #include <dt-bindings/interrupt-controller/irq.h>
> +
> +    i2c {
> +      #address-cells = <1>;
> +      #size-cells = <0>;
> +
> +      pmic@62 {
> +        compatible = "richtek,rt5120";
> +        reg = <0x62>;
> +        interrupts-extended = <&gpio_intc 32 IRQ_TYPE_LEVEL_LOW>;
> +        interrupt-controller;
> +        #interrupt-cells = <1>;
> +        wakeup-source;
> +
> +        regulators {
> +          buck1 {
> +            regulator-name = "rt5120-buck1";
> +            regulator-min-microvolt = <600000>;
> +            regulator-max-microvolt = <1393750>;
> +            regulator-allowed-modes = <0 1>;
> +            regulator-boot-on;
> +          };
> +          buck2 {
> +            regulator-name = "rt5120-buck2";
> +            regulator-min-microvolt = <1100000>;
> +            regulator-max-microvolt = <1100000>;
> +            regulator-allowed-modes = <0 1>;
> +            regulator-always-on;
> +          };
> +          buck3 {
> +            regulator-name = "rt5120-buck3";
> +            regulator-min-microvolt = <1800000>;
> +            regulator-max-microvolt = <1800000>;
> +            regulator-allowed-modes = <0 1>;
> +            regulator-always-on;
> +          };
> +          buck4 {
> +            regulator-name = "rt5120-buck4";
> +            regulator-min-microvolt = <3300000>;
> +            regulator-max-microvolt = <3300000>;
> +            regulator-allowed-modes = <0 1>;
> +            regulator-always-on;
> +          };
> +          ldo {
> +            regulator-name = "rt5120-ldo";
> +            regulator-min-microvolt = <1800000>;
> +            regulator-max-microvolt = <1800000>;
> +            regulator-always-on;
> +          };
> +          exten {
> +            regulator-name = "rt5120-exten";
> +            regulator-min-microvolt = <3000000>;
> +            regulator-max-microvolt = <3000000>;
> +            regulator-always-on;
> +          };
> +        };
> +        powerkey {
> +                status = "okay";

Messed up indentation. No need for status in examples.

> +                compatible = "richtek,rt5120-pwrkey";
> +        };
> +      };
> +    };


Best regards,
Krzysztof

  reply	other threads:[~2022-06-07 11:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  5:52 [PATCH 0/4] Add Richtek RT5120 PMIC support cy_huang
2022-06-07  5:52 ` [PATCH 1/4] dt-binding: mfd: " cy_huang
2022-06-07 11:52   ` Krzysztof Kozlowski [this message]
2022-06-08  2:52     ` ChiYuan Huang
2022-06-08  7:01       ` Krzysztof Kozlowski
2022-06-08  7:25         ` ChiYuan Huang
2022-06-08  7:44           ` Krzysztof Kozlowski
2022-06-07 19:02   ` Mark Brown
2022-06-08  3:04     ` ChiYuan Huang
2022-06-07  5:52 ` [PATCH 2/4] mfd: rt5120: Add Richtek " cy_huang
2022-06-07  5:52 ` [PATCH 3/4] regulator: rt5120: Add PMIC regulator support cy_huang
2022-06-07 19:00   ` Mark Brown
2022-06-08  3:15     ` ChiYuan Huang
2022-06-08 10:12       ` Mark Brown
2022-06-09  6:35         ` ChiYuan Huang
2022-06-10 11:03           ` Mark Brown
2022-06-13  1:49             ` ChiYuan Huang
2022-06-13 11:10               ` Mark Brown
2022-06-07  5:52 ` [PATCH 4/4] input: misc: rt5120: Add power key support cy_huang
2022-06-08  7:03   ` Krzysztof Kozlowski
2022-06-08  7:05     ` Krzysztof Kozlowski

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=96ecca0b-b65c-749d-d66b-33443cacf2e4@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=broonie@kernel.org \
    --cc=cy_huang@richtek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=u0084500@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).