From: Rob Herring <robh@kernel.org>
To: Sven Schwermer <sven@svenschwermer.de>
Cc: pavel@ucw.cz, schuchmann@schleissheimer.de,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, linux-kernel@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org,
Sven Schwermer <sven.schwermer@disruptive-technologies.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: leds: Add multi-color default-intensities property
Date: Mon, 16 May 2022 19:08:20 -0500 [thread overview]
Message-ID: <20220517000820.GA3614766-robh@kernel.org> (raw)
In-Reply-To: <eef2dba9633a860063527628a72f6a4523aaf6cd.1651744128.git.sven.schwermer@disruptive-technologies.com>
On Thu, 05 May 2022 11:50:08 +0200, Sven Schwermer wrote:
> From: Sven Schwermer <sven.schwermer@disruptive-technologies.com>
>
> This allows to assign intensity values to the individual sub LEDs
> (colors) at driver probe time, i.e. most commonly at kernel boot time.
> This is crucial for setting a specific color early in the boot process.
>
> Signed-off-by: Sven Schwermer <sven.schwermer@disruptive-technologies.com>
> ---
>
> Notes:
> V1->V2: no changes
> V2->V3:
> - Use color-intensity mapping instead of simple intensity array
> - Add example DTS snippet
>
> .../bindings/leds/leds-class-multicolor.yaml | 37 +++++++++++++++++++
> 1 file changed, 37 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2022-05-17 0:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 14:09 Initial multicolor LED intensities Sven Schwermer
2022-05-02 20:46 ` Pavel Machek
2022-05-03 11:04 ` [PATCH v1 1/2] dt-bindings: leds: Add multi-color default-intensities property Sven Schwermer
2022-05-03 11:04 ` [PATCH v1 2/2] leds: multicolor: Read " Sven Schwermer
2022-05-03 11:27 ` [PATCH v2 1/2] dt-bindings: leds: Add multi-color " Sven Schwermer
2022-05-03 11:27 ` [PATCH v2 2/2] leds: multicolor: Read " Sven Schwermer
2022-05-03 13:50 ` AW: [PATCH v2 1/2] dt-bindings: leds: Add multi-color " Sven Schuchmann
2022-05-03 18:58 ` Sven Schwermer
2022-05-04 7:17 ` AW: " Sven Schuchmann
2022-05-04 9:24 ` Sven Schwermer
2022-05-08 19:55 ` Jacek Anaszewski
2022-05-10 18:31 ` Sven Schwermer
2022-05-10 22:00 ` Jacek Anaszewski
2022-05-05 9:50 ` [PATCH v3 " Sven Schwermer
2022-05-05 9:50 ` [PATCH v3 2/2] leds: multicolor: Read " Sven Schwermer
2022-05-17 0:08 ` 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=20220517000820.GA3614766-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=schuchmann@schleissheimer.de \
--cc=sven.schwermer@disruptive-technologies.com \
--cc=sven@svenschwermer.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).