Devicetree
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: Conor Dooley <conor@kernel.org>, Lee Jones <lee@kernel.org>,
	Pavel Machek <pavel@kernel.org>
Cc: 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,
	Jonas Rebmann <jre@pengutronix.de>
Subject: Re: [PATCH RFC 1/2] dt-bindings: leds-group-multicolor: Introduce default-intensity
Date: Mon, 13 Jul 2026 10:23:02 +0200	[thread overview]
Message-ID: <cacecf1f-3074-4768-825b-bf143fd36ce2@gmx.net> (raw)
In-Reply-To: <20260709-outsell-undamaged-6c8045d6115f@spud>

Hi all,

Am 09.07.26 um 20:03 schrieb Conor Dooley:
> 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/
sorry, I missed this. Thanks for pointing to this patch. In general i'm 
fine with this approach, but there is something which confuses me.
Looking at the description, there is the statement: [default-intensity] 
"Defaults to 0".
This seems to be correct for the Linux implementation of 
leds-pwm-multicolor, but is this really an expectation along all (multi 
color) LEDs (at least for Linux)?

E.g. leds-group-multicolor init the intensity with the maximum. So all 
users of leds-group-multicolor should specify default-intensity for each 
sub LED to achieve a defined behavior without breaking existing behavior.

Best regards

> 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
>>


  reply	other threads:[~2026-07-13  8:23 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
2026-07-13  8:23     ` Stefan Wahren [this message]
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=cacecf1f-3074-4768-825b-bf143fd36ce2@gmx.net \
    --to=wahrenst@gmx.net \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jjhiblot@traphandler.com \
    --cc=jre@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@kernel.org \
    --cc=robh@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