From: Conor Dooley <conor@kernel.org>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Lee Jones <lee@kernel.org>, Pavel Machek <pavel@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jean-Jacques Hiblot <jjhiblot@traphandler.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH RFC 1/2] dt-bindings: leds-group-multicolor: Introduce default-intensity
Date: Thu, 9 Jul 2026 19:03:48 +0100 [thread overview]
Message-ID: <20260709-outsell-undamaged-6c8045d6115f@spud> (raw)
In-Reply-To: <20260708224652.106632-2-wahrenst@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]
On Thu, Jul 09, 2026 at 12:46:51AM +0200, Stefan Wahren wrote:
> Currently it's not possible to specify the initial color of a LED group
> during boot. So introduce a new property similar to default-brightness,
> which specifies the intensity of each LED in the group.
>
> Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
> ---
> .../devicetree/bindings/leds/leds-group-multicolor.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/leds/leds-group-multicolor.yaml b/Documentation/devicetree/bindings/leds/leds-group-multicolor.yaml
> index 5c9cfa39396b..18b722b807ba 100644
> --- a/Documentation/devicetree/bindings/leds/leds-group-multicolor.yaml
> +++ b/Documentation/devicetree/bindings/leds/leds-group-multicolor.yaml
> @@ -19,6 +19,12 @@ properties:
>
> leds: true
>
> + default-intensity:
> + description:
> + Intensity to be set for each individual LED. Used only during
> + initialization. If the property is not set then max intensity is used.
> + $ref: /schemas/types.yaml#/definitions/uint32-array
Hmm, there's already a property proposed and applied for this:
https://lore.kernel.org/linux-leds/20260605-multicolor-default-v2-1-ed07271df6b0@pengutronix.de/
It only supports a single value, I suspect you'll have to rework this so
as not to conflict with existing property?
leds-group-multicolour imports the common leds properties after all.
Probably the one in common.yaml needs to become an array?
> +
> required:
> - leds
>
> @@ -56,6 +62,7 @@ examples:
> color = <LED_COLOR_ID_RGB>;
> function = LED_FUNCTION_INDICATOR;
> leds = <&led0>, <&led1>, <&led2>;
> + default-intensity = <1 0 0>;
> };
>
> ...
> --
> 2.43.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-07-09 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 22:46 [PATCH RFC 0/2] leds: rgb: leds-group-multicolor: Introduce default-intensity Stefan Wahren
2026-07-08 22:46 ` [PATCH RFC 1/2] dt-bindings: " Stefan Wahren
2026-07-09 18:03 ` Conor Dooley [this message]
2026-07-13 8:23 ` Stefan Wahren
2026-07-13 8:41 ` Jonas Rebmann
2026-07-13 16:34 ` Conor Dooley
2026-07-08 22:46 ` [PATCH RFC 2/2] leds: rgb: leds-group-multicolor: Implement default-intensity Stefan Wahren
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=20260709-outsell-undamaged-6c8045d6115f@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jjhiblot@traphandler.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=robh@kernel.org \
--cc=wahrenst@gmx.net \
/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