From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Krzysztof Kozlowski" <krzk@kernel.org>,
"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>
Cc: "Jacek Anaszewski" <jacek.anaszewski@gmail.com>,
<linux-leds@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-rockchip@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: leds: Clearly mark label property as deprecated
Date: Fri, 15 Aug 2025 14:06:49 +0200 [thread overview]
Message-ID: <DC2ZLORG11W0.1CS78L6F2OV4Q@cknow.org> (raw)
In-Reply-To: <b30905fa-6bd1-47dd-8371-f609d418387b@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]
On Fri Aug 15, 2025 at 1:00 PM CEST, Krzysztof Kozlowski wrote:
> On 15/08/2025 12:47, Diederik de Haas wrote:
>> The text description already mentioned the label property was
>> deprecated, but using the 'deprecated' property makes is clearer and
>> more explicit.
>>
>> Signed-off-by: Diederik de Haas <didi.debian@cknow.org>
>> ---
>> Documentation/devicetree/bindings/leds/common.yaml | 1 +
>> 1 file changed, 1 insertion(+)
>>
>
> Please first read previous discussions:
[I reversed the order of the links so the oldest is first]
> https://lore.kernel.org/all/20221122111124.6828-1-cniedermaier@dh-electronics.com/
Rob: "They ['function' and 'label'] serve 2 different purposes."
> https://lore.kernel.org/all/20240509110545.49889-1-linux@fw-web.de/
Krzysztof: "I don't think there was conclusion to make it deprecated on
last attempt"
I agree.
What I don't understand: Why wasn't the text updated to correct the
incorrect statement about deprecation (that's how I interpret it now)?
Or some other conclusion being made and that that will be reflected in
the text and/or a deprecated property.
Otherwise the confusion remains and then it's just a matter of time
before a 4th person comes along proposing the same patch.
And possibly even more harmful: people use it incorrectly.
There's also this line:
"function-enumerator has no effect when this property is present."
if that is true, and I would assume so as that's what the binding says,
then I messed up even bigger then I already think I did in commit
1631cbdb8089 ("arm64: dts: rockchip: Improve LED config for NanoPi R5S")
resulting in commit
912b1f2a796e ("arm64: dts: rockchip: Drop netdev led-triggers on NanoPi R5S")
... but I'd have expected that to be pointed out in the review.
I can understand that function-enumerator is used in an automatically
generated label when a label doesn't exist, but I'm inclined to think
the same "They serve 2 different purposes" applies here too.
Cheers,
Diederik
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-08-15 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 10:47 [PATCH] dt-bindings: leds: Clearly mark label property as deprecated Diederik de Haas
2025-08-15 11:00 ` Krzysztof Kozlowski
2025-08-15 12:06 ` Diederik de Haas [this message]
2025-08-20 8:14 ` Krzysztof Kozlowski
2025-08-20 10:37 ` Diederik de Haas
2025-08-20 20:43 ` Jacek Anaszewski
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=DC2ZLORG11W0.1CS78L6F2OV4Q@cknow.org \
--to=didi.debian@cknow.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pavel@kernel.org \
--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).