From: Rob Herring <robh@kernel.org>
To: "J. Neuschäfer" <j.ne@posteo.net>
Cc: Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Andrew Davis <afd@ti.com>,
Pavel Machek <pavel@kernel.org>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v2] dt-bindings: leds: Allow differently named multicolor leds
Date: Sat, 12 Apr 2025 12:12:37 -0500 [thread overview]
Message-ID: <20250412171237.GA1347507-robh@kernel.org> (raw)
In-Reply-To: <20250412-multi-led-v2-1-56af86908744@posteo.net>
On Sat, Apr 12, 2025 at 03:04:32PM +0200, J. Neuschäfer wrote:
> In some cases, for example when using multiple instances of
> leds-group-multicolor, 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.
Really, multi-led-0, multi-led-1, etc. would be preferred like we have
in other places.
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: J. Neuschäfer <j.ne@posteo.net>
> ---
> V2:
> - Add Krzysztof's review tag
> - mention leds-group-multicolor in the commit message
> - rebase on 6.15-rc1
>
> Link to v1: https://lore.kernel.org/r/20250209-multi-led-v1-1-5aebccbd2db7@posteo.net
> ---
> Documentation/devicetree/bindings/leds/leds-class-multicolor.yaml | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/leds/leds-class-multicolor.yaml b/Documentation/devicetree/bindings/leds/leds-class-multicolor.yaml
> index bb40bb9e036ee00e06d21e2321ecd5a7d471c408..c22af25b6430be71300c0e37f696cd61112ea190 100644
> --- a/Documentation/devicetree/bindings/leds/leds-class-multicolor.yaml
> +++ b/Documentation/devicetree/bindings/leds/leds-class-multicolor.yaml
> @@ -21,7 +21,9 @@ description: |
>
> properties:
> $nodename:
> - pattern: "^multi-led(@[0-9a-f])?$"
> + oneOf:
> + - pattern: "^multi-led(@[0-9a-f])?$"
> + - pattern: "^multi-led-.*$"
Combine these:
'^multi-led(-.+|@[0-9a-f])?$'
oneOf is best avoided because the error messages aren't so great.
>
> color:
> description: |
>
> ---
> base-commit: 0af2f6be1b4281385b618cb86ad946eded089ac8
> change-id: 20250209-multi-led-9991e205befd
>
> Best regards,
> --
> J. Neuschäfer <j.ne@posteo.net>
>
next prev parent reply other threads:[~2025-04-12 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 13:04 [PATCH v2] dt-bindings: leds: Allow differently named multicolor leds J. Neuschäfer via B4 Relay
2025-04-12 17:12 ` Rob Herring [this message]
2025-04-17 14:35 ` J. Neuschäfer
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=20250412171237.GA1347507-robh@kernel.org \
--to=robh@kernel.org \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j.ne@posteo.net \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=pavel@ucw.cz \
/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).