From: Nam Tran <trannamatk@gmail.com>
To: krzk+dt@kernel.org
Cc: pavel@kernel.org, lee@kernel.org, robh@kernel.org,
conor+dt@kernel.org, corbet@lwn.net, devicetree@vger.kernel.org,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/5] dt-bindings: leds: add TI/National Semiconductor LP5812 LED Driver
Date: Thu, 17 Apr 2025 16:37:40 +0700 [thread overview]
Message-ID: <20250417093740.8466-1-trannamatk@gmail.com> (raw)
In-Reply-To: <878933d0-7062-4b91-ac32-efd5ea190702@kernel.org>
On Thu, 17 Apr 2025, Krzysztof Kozlowski wrote:
>On 17/04/2025 04:06, Nam Tran wrote:
>>
>>>>
>>>>>> +
>>>>>> +patternProperties:
>>>>>> + "^led@[0-9a-b]$":
>>>>>> + type: object
>>>>>> + $ref: common.yaml#
>>>>>> + unevaluatedProperties: false
>>>>>> +
>>>>>> + properties:
>>>>>> + reg:
>>>>>> + minimum: 0
>>>>>> + maximum: 0xb
>>>>>> +
>>>>>> + chan-name:
>>>>>> + $ref: /schemas/types.yaml#/definitions/string
>>>>>> + description: LED channel name
>>>>>
>>>>> My comment stay valid. I don't think LEDs have channels, datasheet also
>>>>> has nothing about channels, so again - use existing properties. Or
>>>>> better drop it - I don't see any point in the name. The reg already
>>>>> defines it.
>>>>
>>>> The channel was named for the output channel to each LED, not the LED channels.
>>>
>>> I don't understand what you want to say. Please explain why existing
>>> label property is not correct here.
>>
>> I understand that the label property is deprecated and that the preferred approach now is to use function and color instead.
>> However, in the case of the LP5812, which is a matrix LED driver, these properties are not a good fit.
>> The LP5812 does not associate each output with a specific function (like "status", "activity"),
>> and the LEDs driven by LP5812 are not fixed to a particular color.
>
>Then use label instead of creating another property. If label is
>deprecated, how creating another property which duplicates the label
>solves anything?
You're right — creating a new property like chan-name does not help
if it duplicates the purpose of the deprecated label property.
I initially created the chan-name property after referring to the existing leds-lp55xx.yaml binding.
However, based on your recommendation, I’ve decided to drop chan-name and the entire subnode as well.
Additionally, I will add the vcc-supply property as mentioned in the last email.
Would this be sufficient for me to submit a new patch?
Best regards,
Nam Tran
next prev parent reply other threads:[~2025-04-17 9:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 14:57 [PATCH v5 0/5] leds: add new LED driver for TI LP5812 Nam Tran
2025-04-14 14:57 ` [PATCH v5 1/5] dt-bindings: leds: add TI/National Semiconductor LP5812 LED Driver Nam Tran
2025-04-14 15:10 ` Krzysztof Kozlowski
2025-04-15 9:53 ` Nam Tran
2025-04-15 9:59 ` Krzysztof Kozlowski
2025-04-17 2:06 ` Nam Tran
2025-04-17 5:43 ` Krzysztof Kozlowski
2025-04-17 9:37 ` Nam Tran [this message]
2025-04-14 14:57 ` [PATCH v5 2/5] " Nam Tran
2025-04-14 14:57 ` [PATCH v5 3/5] docs: ABI: Document LP5812 LED sysfs interfaces Nam Tran
2025-04-14 14:57 ` [PATCH v5 4/5] docs: leds: Document TI LP5812 LED driver Nam Tran
2025-04-14 14:57 ` [PATCH v5 5/5] arm64: dts: Add LP5812 LED node for Raspberry Pi 4 Model B Nam Tran
2025-04-14 15:10 ` Krzysztof Kozlowski
2025-04-15 9:56 ` Nam Tran
2025-04-14 15:05 ` [PATCH v5 0/5] leds: add new LED driver for TI LP5812 Krzysztof Kozlowski
2025-04-18 4:43 ` Nam Tran
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=20250417093740.8466-1-trannamatk@gmail.com \
--to=trannamatk@gmail.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--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@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