From: Rob Herring <robh@kernel.org>
To: Florian Eckert <fe@dev.tdt.de>
Cc: linux-kernel@vger.kernel.org, andy.shevchenko@gmail.com,
devicetree@vger.kernel.org, linux-leds@vger.kernel.org,
Eckert.Florian@googlemail.com, robh+dt@kernel.org, pavel@ucw.cz
Subject: Re: [PATCH v3 2/2] dt: bindings: KTD20xx: Introduce the ktd20xx family of RGB drivers
Date: Wed, 19 Jan 2022 08:47:04 -0600 [thread overview]
Message-ID: <YegkaA49xZONJcrx@robh.at.kernel.org> (raw)
In-Reply-To: <20220117124741.7165-3-fe@dev.tdt.de>
On Mon, 17 Jan 2022 13:47:41 +0100, Florian Eckert wrote:
> Introduce the bindings for the Kinetic KTD2061/58/59/60RGB LED device
> driver. The KTD20xx can control RGB LEDs individually. Because of the
> hardware limitations, only 7 colors and the color black (off) can be set.
>
> Signed-off-by: Florian Eckert <fe@dev.tdt.de>
> ---
> .../bindings/leds/leds-ktd20xx.yaml | 130 ++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 131 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/leds/leds-ktd20xx.yaml
>
Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.
If a tag was not added on purpose, please state why and what changed.
prev parent reply other threads:[~2022-01-19 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 12:47 [PATCH v3 0/2] leds: add ktd20xx LED driver support Florian Eckert
2022-01-17 12:47 ` [PATCH v3 1/2] leds: ktd20xx: Extension of the KTD20xx family of LED drivers from Kinetic Florian Eckert
2022-01-18 10:41 ` Andy Shevchenko
2022-01-17 12:47 ` [PATCH v3 2/2] dt: bindings: KTD20xx: Introduce the ktd20xx family of RGB drivers Florian Eckert
2022-01-19 14:47 ` Rob Herring [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=YegkaA49xZONJcrx@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Eckert.Florian@googlemail.com \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fe@dev.tdt.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.