From: Conor Dooley <conor@kernel.org>
To: Jonas Rebmann <jre@pengutronix.de>
Cc: Stefan Wahren <wahrenst@gmx.net>, 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: Mon, 13 Jul 2026 17:34:49 +0100 [thread overview]
Message-ID: <20260713-undercoat-cranium-c018ab9ab642@spud> (raw)
In-Reply-To: <0e3f38bd-ca70-4136-a313-564267cb9239@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]
On Mon, Jul 13, 2026 at 10:41:53AM +0200, Jonas Rebmann wrote:
> Hi Stefan,
>
> Thanks, for CCing me here.
>
> On 2026-07-13 10:23, Stefan Wahren wrote:
> > 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)?
>
> You are right, sadly the initialization default of some
> multicolor-LED drivers differs.
Hmm, I forget if you had a default in leds common.yaml, but you should
probably remove it in this case and move the default to the individual
led type if so, rather than wait for support in a driver that doesn't
zero initialise.
> > 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.
>
> I agree, once support is added to one of the drivers that doesn't
> zero-initialize, the documentation needs updating (because as you say,
> backwards-compatibilty probably beats consistency here).
>
> I'm also just noticing that my v3 for only the dt-bindings never arrived
> on the list (I think I was on a buggy b4 master), I'll re-send now.
>
> Regards,
> Jonas
>
> --
> Pengutronix e.K. | Jonas Rebmann |
> Steuerwalder Str. 21 | http://www.pengutronix.de/ |
> 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-07-13 16:34 UTC|newest]
Thread overview: 8+ 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
2026-07-13 8:41 ` Jonas Rebmann
2026-07-13 16:34 ` Conor Dooley [this message]
2026-07-08 22:46 ` [PATCH RFC 2/2] leds: rgb: leds-group-multicolor: Implement default-intensity Stefan Wahren
2026-07-23 12:01 ` Lee Jones
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=20260713-undercoat-cranium-c018ab9ab642@spud \
--to=conor@kernel.org \
--cc=conor+dt@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 \
--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