From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nam Tran <trannamatk@gmail.com>
Cc: lee@kernel.org, pavel@kernel.org, gregkh@linuxfoundation.org,
rdunlap@infradead.org, christophe.jaillet@wanadoo.fr,
krzk+dt@kernel.org, robh@kernel.org, conor+dt@kernel.org,
corbet@lwn.net, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v18 1/3] dt-bindings: leds: add TI/National Semiconductor LP5812 LED Driver
Date: Mon, 24 Nov 2025 09:02:14 +0100 [thread overview]
Message-ID: <74d6319c-535f-4409-a3c4-299ab946af54@kernel.org> (raw)
In-Reply-To: <20251124-resolute-wrasse-of-wholeness-aed84d@kuoka>
On 24/11/2025 08:57, Krzysztof Kozlowski wrote:
> On Mon, Nov 24, 2025 at 02:10:40AM +0700, Nam Tran wrote:
>> The LP5812 is a 4x3 RGB LED driver with an autonomous animation
>> engine and time-cross-multiplexing (TCM) support for up to 12 LEDs
>> or 4 RGB LEDs. It supports both analog (256 levels) and PWM (8-bit)
>> dimming, including exponential PWM for smooth brightness control.
>>
>> Signed-off-by: Nam Tran <trannamatk@gmail.com>
>> ---
>> .../devicetree/bindings/leds/ti,lp5812.yaml | 251 ++++++++++++++++++
>> MAINTAINERS | 6 +
>> 2 files changed, 257 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/leds/ti,lp5812.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/leds/ti,lp5812.yaml b/Documentation/devicetree/bindings/leds/ti,lp5812.yaml
>> new file mode 100644
>> index 000000000000..ea9d6ae92344
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/leds/ti,lp5812.yaml
>> @@ -0,0 +1,251 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/leds/ti,lp5812.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: TI LP5812 4x3 Matrix RGB LED Driver with Autonomous Control
>> +
>> +maintainers:
>> + - Nam Tran <trannamatk@gmail.com>
>> +
>> +description: |
>> + The LP5812 is a 4x3 matrix RGB LED driver with I2C interface
>> + and autonomous animation engine control.
>> + 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
>> +
>> + ti,scan-mode:
>> + description: |
>> + Selects the LED scan mode of the LP5812. The device supports
>> + three modes:
>> + - Direct-drive mode (by default if 'ti,scan-mode' is omitted)
>> + drives up to 4 LEDs directly by internal current sinks (LED0-LED3).
>> + - TCM-drive mode ("tcm:<n>:<order...>") drives up to 12 LEDs
>> + (4 RGB) using 1-4 scan multiplexing. The <n> specifies the number
>> + of scans (1-4), and <order...> defines the scan order of the outputs.
>> + - Mix-drive mode ("mix:<n>:<direct>:<order...>") combines
>> + direct-drive and TCM-drive outputs. The <n> specifies the number
>> + of scans, <direct> selects the direct-drive outputs, and <order...>
>> + defines the scan order.
>> + $ref: /schemas/types.yaml#/definitions/string
>> + pattern: '^(tcm|mix):[1-4](:[0-3]){1,4}$'
>> +
>> + vcc-supply:
>> + description: Regulator providing power to the 'VCC' pin.
>> +
>> + "#address-cells":
>> + const: 1
>> +
>> + "#size-cells":
>> + const: 0
>> +
>> +patternProperties:
>> + "^led@[0-3]$":
>> + type: object
>> + $ref: common.yaml#
>> + unevaluatedProperties: false
>> +
>> + properties:
>> + reg:
>> + minimum: 0
>> + maximum: 3
>> +
>> + required:
>> + - reg
>> + - label
>
> No, why? That's legacy property and color and function are preferred.
>
>> +
>> + "^multi-led@[4-7]$":
>> + type: object
>> + $ref: leds-class-multicolor.yaml#
>> + unevaluatedProperties: false
>> +
>> + properties:
>> + reg:
>> + minimum: 4
>> + maximum: 7
>> +
>> + "#address-cells":
>> + const: 1
>> +
>> + "#size-cells":
>> + const: 0
>> +
>> + patternProperties:
>> + "^led@[4-9a-f]$":
>> + type: object
>> + $ref: common.yaml#
>> + unevaluatedProperties: false
>> +
>> + properties:
>> + reg:
>> + minimum: 4
>> + maximum: 15
>> +
>> + required:
>> + - reg
>> +
>> + required:
>> + - reg
>> + - label
>
> Why? Same problems.
>
> Please stop making continuous changes to the binding.
>
>
>> +
>> +required:
>> + - compatible
>> + - reg
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/leds/common.h>
>> +
>> + i2c {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + led-controller@1b {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + compatible = "ti,lp5812";
>> + reg = <0x1b>;
>> + ti,scan-mode = "tcm:4:0:1:2:3";
>> + vcc-supply = <&vdd_3v3_reg>;
>> +
>> + led@0 {
>> + reg = <0x0>;
>> + label = "LED0";
>> + led-max-microamp = <25500>;
>> + };
>> +
>> + led@1 {
>> + reg = <0x1>;
>> + label = "LED1";
>
> Completely useless label... You require labels, so people need to write
> something but since they do not know what to write they call LED 1 a
> LED1. This is just not helping.
>
> Use color and function properties. Same everywhere else.
>
And now I went to older versions and I see they were correct - you had
color! You replace correct code with wrong one and drop review. This
patchset is not really improving.
BTW, You actually received review also at v6, so this was reviewed 3 or
more times. Way too many times.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-24 8:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-23 19:10 [PATCH v18 0/3] leds: add new LED driver for TI LP5812 Nam Tran
2025-11-23 19:10 ` [PATCH v18 1/3] dt-bindings: leds: add TI/National Semiconductor LP5812 LED Driver Nam Tran
2025-11-24 7:30 ` Krzysztof Kozlowski
2025-11-24 7:55 ` Krzysztof Kozlowski
2025-11-24 7:57 ` Krzysztof Kozlowski
2025-11-24 8:02 ` Krzysztof Kozlowski [this message]
2025-11-26 16:55 ` Nam Tran
2025-11-23 19:10 ` [PATCH v18 2/3] leds: add basic support for " Nam Tran
2025-11-25 13:48 ` Lee Jones
2025-11-26 16:00 ` Nam Tran
2025-11-27 11:32 ` Lee Jones
2025-11-27 14:58 ` Nam Tran
2025-11-23 19:10 ` [PATCH v18 3/3] docs: leds: Document TI LP5812 LED driver Nam Tran
2025-11-23 19:20 ` Randy Dunlap
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=74d6319c-535f-4409-a3c4-299ab946af54@kernel.org \
--to=krzk@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).