From: Krzysztof Kozlowski <krzk@kernel.org>
To: jeff_chang@richtek.com, lgirdwood@gmail.com, broonie@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: regulator: Add Richtek RTR5133 Support
Date: Tue, 22 Jul 2025 11:04:51 +0200 [thread overview]
Message-ID: <f4505b19-3496-4fab-ad74-d190d847eb17@kernel.org> (raw)
In-Reply-To: <20250722083543.2730796-1-jeff_chang@richtek.com>
On 22/07/2025 10:34, jeff_chang@richtek.com wrote:
> From: Jeff Chang <jeff_chang@richtek.com>
>
> Add bindings for Richtek RT5133 IC Controlled PMIC
Subject - RTR or RT? Google tells me nothing about RTR.
>
> Signed-off-by: Jeff Chang <jeff_chang@richtek.com>
> ---
>
> PATCH v4
> 1. Add commit message and also /script/checkpatch --strict to fix warning.
> 2. Using subject prefixes matching dt-binding subsystem.
> 3. Re-order patches. DT patch before driver patch.
> 4. Fix description of yaml.
> 5. Add more description for base regulator.
> 6. Drop regulator-compatible proeprty.
> 7. Add prefix for vendor property richtek,oc-shutdown-all and richtek,pgb-shutdown-all.
> 8. Add more description for shutdown-all property.
> 9. Interrupts-extended -> interrupts.
> 10. pio->gpio for proper defines.
> 11. Drop unused labels. Keep rt5133_ldo1 label for ldo7 and ldo8.
>
> .../bindings/regulator/richtek,rt5133.yaml | 175 ++++++++++++++++++
> 1 file changed, 175 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/regulator/richtek,rt5133.yaml
>
> diff --git a/Documentation/devicetree/bindings/regulator/richtek,rt5133.yaml b/Documentation/devicetree/bindings/regulator/richtek,rt5133.yaml
> new file mode 100644
> index 000000000000..0da725596a87
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/richtek,rt5133.yaml
> @@ -0,0 +1,175 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/regulator/richtek,rt5133.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Richtek RT5133 PMIC Regulator
> +
> +maintainers:
> + - ShihChia Chang <jeff_chang@richtek.com>
> +
> +description:
> + The RT5133 is an integrated Power Management IC for portable devices, featuring
> + 8 LDOs and 3 GPOs. It allows programmable output voltages, soft-start times,
> + and protections via I2C. GPO operation depends on LDO1 voltage.
> +
> +properties:
> + compatible:
> + enum:
> + - richtek,rt5133
> +
> + reg:
> + maxItems: 1
> +
> + enable-gpios:
> + maxItems: 1
> +
> + wakeup-source: true
> +
> + interrupts:
> + maxItems: 1
> +
> + gpio-controller: true
> +
> + "#gpio-cells":
> + const: 2
> +
> + regulators:
> + type: object
> + additionalProperties: false
> +
> + properties:
> + base:
> + type: object
> + $ref: regulator.yaml#
> + unevaluatedProperties: false
> + description:
> + Properties for base regulator which control force-off base circuit.
> + Base circuit is the power source for LDO1~LDO6. Disabling it will
> + reduce IQ for Chip.
I don't understand what this regulator is for. Your example is also
incomplete - missing min/max constraints like voltage.
Explain, what is this output pin? I already asked for explanations. I
have diagram in front of me, so explain precisely instead of sending THE
SAME again - which pin is it?
Also, what is IQ? Except Intelligence Quotient?
> +
> + properties:
> + richtek,oc-shutdown-all:
> + type: boolean
> + description:
> + Anyone of LDO is in OC state, shut down all channels to protect CHIP.
> + Without this property, only shut down the OC LDO channel.
I don't understand this. I also do not understand why this is property
of "base" not the chip itself...
So don't send next version with the same.
> +
> + richtek,pgb-shutdown-all:
> + type: boolean
> + description:
> + Anyone of LDO is in PGB state, shut down all channels to protect CHIP.
CHIP is an acronym? Or chip?
> + Without this property, only shut down the PGB LDO channel.
> +
> + required:
> + - regulator-name
> +
> + patternProperties:
> + "^ldo([1-6])$":
> + type: object
> + $ref: regulator.yaml#
> + unevaluatedProperties: false
> + description:
> + Properties for single LDO regulator
> +
> + required:
> + - regulator-name
> +
> + "^ldo([7-8])$":
> + type: object
> + $ref: regulator.yaml#
> + unevaluatedProperties: false
> + description:
> + Properties for single LDO regulator
> +
> + properties:
> + rt5133-ldo1-supply:
supplies do not have vendor prefixes.
> + description: |
> + Only for ldo7 ldo8, pvin7 and pvin8 reference design are RT5133 ldo1.
> + If not connect to ldo1 vout, this property for pvin7 and pvin8 is necessary.
I don't understand why LDO1 supply is here.
Again, which pin is it?
> +
> + required:
> + - regulator-name
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - wakeup-source
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + rt5133@18 {
Nothing improved.
> + compatible = "richtek,rt5133";
> + reg = <0x18>;
> + wakeup-source;
> + interrupts-extended = <&gpio 187 0x0>;
Nothing improved
Implement previous comments and respond to each of them to confirm you
understood them.
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-22 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 8:34 jeff_chang
2025-07-22 8:34 ` [PATCH v4 2/2] regulator: rt5133: Add RT5133 PMIC regulator Support jeff_chang
2025-07-22 9:04 ` Krzysztof Kozlowski [this message]
2025-07-22 11:54 ` [PATCH v4 1/2] dt-bindings: regulator: Add Richtek RTR5133 Support Mark Brown
2025-07-23 2:32 ` jeff_chang(張世佳)
2025-07-23 6:19 ` Krzysztof Kozlowski
2025-07-23 6:47 ` jeff_chang
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=f4505b19-3496-4fab-ad74-d190d847eb17@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jeff_chang@richtek.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®