From: Rob Herring <robh@kernel.org>
To: sven@svenschwermer.de
Cc: pavel@ucw.cz, devicetree@vger.kernel.org,
Sven Schwermer <sven.schwermer@disruptive-technologies.com>,
linux-pwm@vger.kernel.org, robh+dt@kernel.org, post@lespocky.de,
linux-leds@vger.kernel.org, thierry.reding@gmail.com,
lee.jones@linaro.org, u.kleine-koenig@pengutronix.de,
andy.shevchenko@gmail.com
Subject: Re: [PATCH v7 2/3] dt-bindings: leds: Add multicolor PWM LED bindings
Date: Wed, 16 Feb 2022 17:56:47 -0600 [thread overview]
Message-ID: <Yg2PPwXpE9OUd85d@robh.at.kernel.org> (raw)
In-Reply-To: <20220210075908.120496-2-sven@svenschwermer.de>
On Thu, 10 Feb 2022 08:59:07 +0100, sven@svenschwermer.de wrote:
> From: Sven Schwermer <sven.schwermer@disruptive-technologies.com>
>
> This allows to group multiple PWM-connected monochrome LEDs into
> multicolor LEDs, e.g. RGB LEDs.
>
> Signed-off-by: Sven Schwermer <sven.schwermer@disruptive-technologies.com>
> ---
>
> Notes:
> Changes in v7:
> * Added newlines
> * Reorder slightly
> * Rename top-level node in example
>
> Changes in v6:
> * Fix device tree binding schema
>
> Changes in v5:
> * (no changes)
>
> Changes in v4:
> * (no changes)
>
> Changes in v3:
> * Remove multi-led unit name
>
> .../bindings/leds/leds-pwm-multicolor.yaml | 79 +++++++++++++++++++
> 1 file changed, 79 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/leds/leds-pwm-multicolor.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-02-16 23:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 7:59 [PATCH v7 1/3] dt-bindings: leds: Optional multi-led unit address sven
2022-02-10 7:59 ` [PATCH v7 2/3] dt-bindings: leds: Add multicolor PWM LED bindings sven
2022-02-16 23:56 ` Rob Herring [this message]
2022-02-10 7:59 ` [PATCH v7 3/3] leds: Add PWM multicolor driver sven
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=Yg2PPwXpE9OUd85d@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=post@lespocky.de \
--cc=robh+dt@kernel.org \
--cc=sven.schwermer@disruptive-technologies.com \
--cc=sven@svenschwermer.de \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).