From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-pwm@vger.kernel.org,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Lee Jones" <lee@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Uwe Kleine-König" <ukleinek@kernel.org>
Subject: Re: [PATCH v3 1/4] dt-bindings: Add bindings for the Analog Devices ADP5585
Date: Sun, 2 Jun 2024 18:50:15 +0300 [thread overview]
Message-ID: <20240602155015.GI6683@pendragon.ideasonboard.com> (raw)
In-Reply-To: <de6c28c6-3139-441e-8738-c8842b9a274b@kernel.org>
Hi Krzysztof,
On Sun, Jun 02, 2024 at 05:31:04PM +0200, Krzysztof Kozlowski wrote:
> On 02/06/2024 17:24, Laurent Pinchart wrote:
> > The ADP5585 is a 10/11 input/output port expander with a built in keypad
> > matrix decoder, programmable logic, reset generator, and PWM generator.
> > These bindings model the device as an MFD, and support the GPIO expander
> > and PWM functions.
>
> Please use subject prefixes matching the subsystem, e.g. dt-bindings: mfd:
>
> A nit, subject: drop second/last, redundant "bindings for". The
> "dt-bindings" prefix is already stating that these are bindings.
> See also:
> https://elixir.bootlin.com/linux/v6.7-rc8/source/Documentation/devicetree/bindings/submitting-patches.rst#L18
I'll do that. It would be nice if someone could teach checkpatch about
this rule.
> > These bindings support the GPIO and PWM functions.
> >
> > Drop the existing adi,adp5585 and adi,adp5585-02 compatible strings from
> > trivial-devices.yaml. They have been added there by mistake as the
> > driver that was submitted at the same time used different compatible
> > strings. We can take them over safely.
> >
>
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + i2c {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + mfd@34 {
>
> mfd is Linuxism, so this should be probably "io-expander" or something
> similar.
Sure.
> > + compatible = "adi,adp5585-00", "adi,adp5585";
> > + reg = <0x34>;
> > +
> > + vdd-supply = <®_3v3>;
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2024-06-02 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 15:24 [PATCH v3 0/4] ADP5585 GPIO expander, PWM and keypad controller support Laurent Pinchart
2024-06-02 15:24 ` [PATCH v3 1/4] dt-bindings: Add bindings for the Analog Devices ADP5585 Laurent Pinchart
2024-06-02 15:31 ` Krzysztof Kozlowski
2024-06-02 15:50 ` Laurent Pinchart [this message]
2024-06-02 15:24 ` [PATCH v3 2/4] mfd: adp5585: Add Analog Devices ADP5585 core support Laurent Pinchart
2024-06-02 15:24 ` [PATCH v3 3/4] gpio: adp5585: Add Analog Devices ADP5585 support Laurent Pinchart
2024-06-03 8:17 ` Bartosz Golaszewski
2024-06-02 15:24 ` [PATCH v3 4/4] pwm: " Laurent Pinchart
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=20240602155015.GI6683@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ukleinek@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