[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAA6zWZ+x9cj4kOTepYNZ+9anCruSP+dgdsyux6iVKF+vN1Heaw@mail.gmail.com>
Date: Mon, 21 Jul 2025 13:26:52 +0100
From: Pawel Zalewski <pzalewski@...goodpenguin.co.uk>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Lee Jones <lee@...nel.org>, Pavel Machek <pavel@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, linux-leds@...r.kernel.org,
linux-kernel@...r.kernel.org, Pavel Machek <pavel@....cz>, devicetree@...r.kernel.org,
Lucca Fachinetti <luccafachinetti@...il.com>
Subject: Re: [PATCH v5 1/3] dt-bindings: leds: is31fl32xx: convert the binding
to yaml
> 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])$
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
I suppose.
Kind regards,
Pawel
Powered by blists - more mailing lists