From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pawel Zalewski <pzalewski@thegoodpenguin.co.uk>
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>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
Pavel Machek <pavel@ucw.cz>,
devicetree@vger.kernel.org,
Lucca Fachinetti <luccafachinetti@gmail.com>
Subject: Re: [PATCH v5 1/3] dt-bindings: leds: is31fl32xx: convert the binding to yaml
Date: Mon, 21 Jul 2025 14:34:36 +0200 [thread overview]
Message-ID: <f327a84d-8979-438d-aa05-c64472a93c16@kernel.org> (raw)
In-Reply-To: <CAA6zWZ+x9cj4kOTepYNZ+9anCruSP+dgdsyux6iVKF+vN1Heaw@mail.gmail.com>
On 21/07/2025 14:26, Pawel Zalewski wrote:
>> This still does not match min/max constraints. You already got the
>> comment on this and nothing improved.
>
> It was not clear to me what you are after, so you want the pattern to be:
>
> ^led@(?:[1-9a-f]|1[0-9a-f]|2[0-4])$
led@([1-9a-f]|1[0-9a-f]|2[0-4])$
should be enough
>
> So the range of the unit@ string is controlled via the pattern
> orthogonal to reg,
> the range of the reg property explicitly via minimum/maximum which are decimal,
> despite the fact that the reg itself can be a hex value, which is
> preferred for readability
Yes, just write min/max decimal in the list. It's not an address, but index.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-21 12:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 10:55 [PATCH v5 0/3] Add support for is31fl3236a LED controller Pawel Zalewski
2025-07-21 10:55 ` [PATCH v5 1/3] dt-bindings: leds: is31fl32xx: convert the binding to yaml Pawel Zalewski
2025-07-21 11:16 ` Krzysztof Kozlowski
2025-07-21 12:26 ` Pawel Zalewski
2025-07-21 12:34 ` Krzysztof Kozlowski [this message]
2025-07-21 10:55 ` [PATCH v5 2/3] dt-bindings: leds: issi,is31fl3236: add support for is31fl3236a Pawel Zalewski
2025-07-21 11:16 ` Krzysztof Kozlowski
2025-07-21 12:27 ` Pawel Zalewski
2025-07-21 10:55 ` [PATCH v5 3/3] leds/leds-is31fl32xx: " Pawel Zalewski
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=f327a84d-8979-438d-aa05-c64472a93c16@kernel.org \
--to=krzk@kernel.org \
--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=luccafachinetti@gmail.com \
--cc=pavel@kernel.org \
--cc=pavel@ucw.cz \
--cc=pzalewski@thegoodpenguin.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).