From: like@awinic.com
To: krzysztof.kozlowski@linaro.org
Cc: broonie@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
lgirdwood@gmail.com, liangdong@awinic.com, like@awinic.com,
linux-kernel@vger.kernel.org, liweilei@awinic.com,
robh+dt@kernel.org, wangweidong.a@awinic.com
Subject: Re: [PATCH V1 2/2] regulator: aw37503: add device-tree binding
Date: Fri, 28 Jul 2023 03:19:02 +0000 [thread overview]
Message-ID: <20230728031902.1478890-1-like@awinic.com> (raw)
In-Reply-To: <8bd37e11-2861-7877-0321-3f89cd088532@linaro.org>
Hello Krzysztof Kozlowski,
Thank you very much for your advice.
> On 26/07/2023 10:16, like@awinic.com wrote:
> > From: Alec Li <like@awinic.com>
> >
> > Add aw37503 regulator device-tree binding documentation
>
> subject rather like:
> regulator: dt-bindings: Add Awinic aw37503
I will modify it as suggested.
> >
> > Signed-off-by: Alec Li <like@awinic.com>
> > ---
> > .../bindings/regulator/awinic,aw37503.yaml | 73 +++++++++++++++++++
> > 1 file changed, 73 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/regulator/awinic,aw37503.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/regulator/awinic,aw37503.yaml b/Documentation/devicetree/bindings/regulator/awinic,aw37503.yaml
> > new file mode 100644
> > index 000000000000..0cd6fb001e20
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/regulator/awinic,aw37503.yaml
> > @@ -0,0 +1,73 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/regulator/awinic,aw37503.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Awinic AW37503 Voltage Regulator
> > +
> > +maintainers:
> > + - Alec Li <like@awinic.com>
> > +
> > +description: |
>
> Do not need '|' unless you need to preserve formatting.
I will modify it as suggested.
> > + The AW37503 is dual voltage regulator, designed to support positive/negative
> > + supply for driving TFT-LCD panels. It support software-configurable output
> > + switching and monitoring. The output voltages can be programmed via an I2C
> > + compatible interface.
> > +
> > +properties:
> > + compatible:
> > + const:
> > + - awinic,aw37503
>
> This has to be in one line. As pointed out by Rob's bot: please test it
> before sending.
I will test it before sending and modify it as suggested.
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + patternProperties:
>
> <sigh>
>
> > + "^out[pn]$":
> > + type: object
> > + $ref: regulator.yaml#
> > + unvaluatedproperties: false
> > +
> > + required:
> > + - regulator-name
> > + - enable-gpios
>
> regulator.yaml does not define enable-gpios, so you must define it in
> properties.
I will modify it as suggested.
> > +
> > + additionalProperties: false
>
> Drop, you already have unevaluatedProperties.
I will modify it as suggested.
> > +
> > +required:
> > + - compatible
> > + - reg
> > + - outp
> > + - outn
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + #include <dt-bindings/gpio/gpio.h>
> > +
> > + i2c {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + aw37503@3e {
>
> Node names should be generic. See also an explanation and list of
> examples (not exhaustive) in DT specification:
> https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
I will modify it as suggested.
Best regards,
Alec Li
prev parent reply other threads:[~2023-07-28 3:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 8:16 [PATCH V1 0/2] regulator: aw37503: add regulator driver for AWINIC AW37503 like
2023-07-26 8:16 ` [PATCH V1 1/2] " like
2023-07-26 11:16 ` Krzysztof Kozlowski
2023-07-28 3:19 ` like
2023-07-26 11:41 ` Mark Brown
2023-07-28 3:20 ` like
2023-07-26 20:13 ` Christophe JAILLET
2023-07-28 3:20 ` like
2023-07-26 8:16 ` [PATCH V1 2/2] regulator: aw37503: add device-tree binding like
2023-07-26 10:52 ` Rob Herring
2023-07-28 3:18 ` like
2023-07-26 11:15 ` Krzysztof Kozlowski
2023-07-28 3:19 ` like [this message]
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=20230728031902.1478890-1-like@awinic.com \
--to=like@awinic.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=liangdong@awinic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liweilei@awinic.com \
--cc=robh+dt@kernel.org \
--cc=wangweidong.a@awinic.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
all inboxes | Powered by JetHome®