From: "J. Neuschäfer" <j.ne@posteo.net>
To: Lee Jones <lee@kernel.org>
Cc: j.ne@posteo.net, Pavel Machek <pavel@ucw.cz>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Andrew Davis <afd@ti.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: leds: Allow differently named multicolor leds
Date: Tue, 11 Feb 2025 18:50:40 +0000 [thread overview]
Message-ID: <Z6ucAFNauWkhfYZr@probook> (raw)
In-Reply-To: <20250211144300.GW1868108@google.com>
On Tue, Feb 11, 2025 at 02:43:00PM +0000, Lee Jones wrote:
> On Sun, 09 Feb 2025, J. Neuschäfer via B4 Relay wrote:
>
> > From: "J. Neuschäfer" <j.ne@posteo.net>
> >
> > In some cases, a board may have multiple multi-leds, which can't be
> > distinguished by unit address. In such cases it should be possible to
> > name them differently, for example multi-led-a and multi-led-b.
> > This patch adds another node name pattern to leds-class-multicolor.yaml
> > to allow such names.
>
> Which H/W needs this? Is it upstream? Where is the doc / usage?
I encountered this situation while upstreaming the LANCOM NWAPP2 board,
which has multiple LED-group-based multicolor LEDs:
https://lore.kernel.org/lkml/20250102-mpc83xx-v1-16-86f78ba2a7af@posteo.net/
Since they are based on leds-group-multicolor, they don't have a unit
address, but there is more than one on the same level (as direct
sub-nodes of the DT root node).
I can add a comment about node names, if that's desired, e.g.:
If multiple multi-color LEDs exist on the same level, they can be
differentiated by unit-address (e.g. multi-led@abc0) or name
(e.g. multi-led-power).
Such as a comment doesn't exist currently either; the existing
"^multi-led(@[0-9a-f])?$" pattern is not documented in prose.
Best regards,
J. Neuschäfer
>
> > Signed-off-by: J. Neuschäfer <j.ne@posteo.net>
> > ---
> > Documentation/devicetree/bindings/leds/leds-class-multicolor.yaml | 4 +++-
[...]
> > + - pattern: "^multi-led(@[0-9a-f])?$"
> > + - pattern: "^multi-led-.*$"
next prev parent reply other threads:[~2025-02-11 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-09 22:06 [PATCH] dt-bindings: leds: Allow differently named multicolor leds J. Neuschäfer
2025-02-09 22:06 ` J. Neuschäfer via B4 Relay
2025-02-11 14:43 ` Lee Jones
2025-02-11 18:50 ` J. Neuschäfer [this message]
2025-02-11 19:10 ` Krzysztof Kozlowski
2025-02-16 18:49 ` J. Neuschäfer
2025-02-11 19:11 ` Krzysztof Kozlowski
2025-02-17 10:58 ` Krzysztof Kozlowski
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=Z6ucAFNauWkhfYZr@probook \
--to=j.ne@posteo.net \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.