From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alina Yu <alina_yu@richtek.com>
Cc: broonie@kernel.org, linux-kernel@vger.kernel.org, cy_huang@richtek.com
Subject: Re: [PATCH v2 1/2] regulator: dt-bindings: rtq2208: Add Richtek RTQ2208 SubPMIC
Date: Thu, 6 Jul 2023 13:04:25 +0200 [thread overview]
Message-ID: <51090bca-0fe2-7cb5-e5a6-7ce9d41bf506@kernel.org> (raw)
In-Reply-To: <20230706103040.GA32138@linuxcarl2.richtek.com>
On 06/07/2023 12:30, Alina Yu wrote:
>>> +
>>> + regulator-state-(mem):
>>
>> That's not a pattern.
>>
>
> Should I revise that like this ?
>
> patternProperties:
> "^regulator-state-mem$":
It's still not a pattern, but a regular property, so keep it in properties.
I don't even understand what you want to say with this. You put it
outside of any regulator. I don't think this was tested at all. :(
>
>
>>> + type: object
>>> + additionalProperties: true
>>
>> Why?
>
> Does "additionalProperties: true" mean I need to define my own property ?
No.
> If yes, I misunderstood additionalProperties as properties like "regulator-on-in-suspend" or "regulator-mode".
Please open recent regulator bindings and use them as example.
>
>>
>>> + properties:
>>> + regulator-on-in-suspend: false
>>> + regulator-mode: false
>>> +
>>> +required:
>>> + - compatible
>>> + - reg
>>> + - regulators
>>> +
>>> +unevaluatedProperties: false
>>> +
>>> +examples:
>>> + - |
>>> + #include <dt-bindings/interrupt-controller/irq.h>
>>> + i2c {
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> +
>>> + rtq2208@10 {
>>
>> Node names should be generic. See also explanation and list of examples
>> in DT specification:
>> https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
>>
>
> I'll modify the node name to
>
> regulator@10
If this is PMIC, then "pmic" as name.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-07-06 11:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 15:27 [PATCH v2 0/2] Add Richtek RTQ2208 SubPMIC support alina_yu
2023-07-05 15:27 ` [PATCH v2 1/2] regulator: dt-bindings: rtq2208: Add Richtek RTQ2208 SubPMIC alina_yu
2023-07-05 17:58 ` Krzysztof Kozlowski
2023-07-06 10:30 ` Alina Yu
2023-07-06 11:04 ` Krzysztof Kozlowski [this message]
2023-07-10 3:08 ` Alina Yu
2023-07-10 6:02 ` Krzysztof Kozlowski
2023-07-10 7:23 ` Alina Yu
2023-07-05 15:27 ` [PATCH v2 2/2] regulator: rtq2208: Add Richtek RTQ2208 SubPMIC driver alina_yu
2023-07-18 8:40 ` Alina Yu
2023-07-18 14:16 ` Mark Brown
2023-07-19 4:29 ` Alina Yu
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=51090bca-0fe2-7cb5-e5a6-7ce9d41bf506@kernel.org \
--to=krzk@kernel.org \
--cc=alina_yu@richtek.com \
--cc=broonie@kernel.org \
--cc=cy_huang@richtek.com \
--cc=linux-kernel@vger.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
Powered by JetHome