From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nam Tran <trannamatk@gmail.com>, 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: Tue, 15 Apr 2025 11:59:33 +0200 [thread overview]
Message-ID: <a22eff98-86db-47db-a310-5d00dcba14fa@kernel.org> (raw)
In-Reply-To: <20250415095358.8044-1-trannamatk@gmail.com>
On 15/04/2025 11:53, Nam Tran wrote:
> On Mon, 14 Apr 2025, Krzysztof Kozlowski wrote:
>
>> On 14/04/2025 16:57, Nam Tran wrote:
>>> +
>>> +description: |
>>> + The LP5812 is an I2C LED Driver that can support LED matrix 4x3.
>>> + For more product information please see the link below:
>>> + https://www.ti.com/product/LP5812#tech-docs
>>> +
>>> +properties:
>>> + compatible:
>>> + const: ti,lp5812
>>> +
>>> + reg:
>>> + maxItems: 1
>>> +
>>> + "#address-cells":
>>> + const: 1
>>> +
>>> + "#size-cells":
>>> + const: 0
>>
>> No need for supply?
>
> Since the hardware uses an external power supply,
> we decide not to include the supply property in the binding.
So there is power supply? If so, must be in the binding. Bindings
describe given hardware (LP5812), not your particular board/setup.
>
>>> +
>>> +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.
> They are not required properties because we can control entirely the LEDs of LP5812 through the indexes (regs property),
I did not ask about this.
> but the person who wants to develop LP5812's matrix-related features can use the "channels" for easy mapping.
easy mapping of what? Please show me the usage.
>
>>
>> However after dropping this, your example has nodes with only reg -
>> what's the point of them? Why no properties from common.yaml are
>> applicable? If they are not applicable, then the entire subnode should
>> be dropped - you don't need them to describe the hardware.
>
> Actually, the "color" property can be applied, but the LP5812 is a matrix LED,
> so specifying a particular LED color is not necessary when developing LP5812 features.
This does not help me much and based on this I see no points in
describing individual LEDs, because the only missing information is
number of them but even that is fixed for given device, isn't it?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-15 9:59 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 [this message]
2025-04-17 2:06 ` Nam Tran
2025-04-17 5:43 ` Krzysztof Kozlowski
2025-04-17 9:37 ` Nam Tran
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=a22eff98-86db-47db-a310-5d00dcba14fa@kernel.org \
--to=krzk@kernel.org \
--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 \
--cc=trannamatk@gmail.com \
/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