From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nam Tran <trannamatk@gmail.com>,
pavel@kernel.org, lee@kernel.org, krzk+dt@kernel.org,
robh@kernel.org, conor+dt@kernel.org, corbet@lwn.net
Cc: devicetree@vger.kernel.org, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/5] dt-bindings: leds: add TI/National Semiconductor LP5812 LED Driver
Date: Sun, 6 Apr 2025 13:59:53 +0200 [thread overview]
Message-ID: <eac877d0-2fd3-44cf-8917-910042cdcec9@kernel.org> (raw)
In-Reply-To: <20250405183246.198568-2-trannamatk@gmail.com>
On 05/04/2025 20:32, Nam Tran wrote:
> +properties:
> + compatible:
> + const: ti,lp5812
> +
> + reg:
> + maxItems: 1
> + description:
> + I2C slave address
> + lp5812/12- 0x1b
Drop description, redundant.
> +
> + "#address-cells":
> + const: 1
> +
> + "#size-cells":
> + const: 0
> +
> +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
Isn't this existing label property? Or node name? You don't need this
and instead whatever currently LED subsystem is expecting (label got
discouraged so maybe there is something else now).
There is no multi-led support in the device? Datasheet this can work as
matrix and as direct drive of 4 LEDs, so binding looks incomplete. Not
sure what you exactly miss here - check other recent devices with
similar features.
> +
> + required:
> + - reg
> +
> +required:
> + - compatible
> + - reg
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/leds/common.h>
> +
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + led-controller@1b {
> + compatible = "ti,lp5812";
> + reg = <0x1b>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + led@0 {
> + reg = <0x0>;
> + chan-name = "a0";
Mixed up indentation.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-06 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 18:32 [PATCH v4 0/5] leds: add new LED driver for TI LP5812 Nam Tran
2025-04-05 18:32 ` [PATCH v4 1/5] dt-bindings: leds: add TI/National Semiconductor LP5812 LED Driver Nam Tran
2025-04-06 11:59 ` Krzysztof Kozlowski [this message]
2025-04-10 15:59 ` Nam Tran
2025-04-05 18:32 ` [PATCH v4 2/5] " Nam Tran
2025-04-06 22:35 ` kernel test robot
2025-04-05 18:32 ` [PATCH v4 3/5] docs: ABI: Document LP5812 LED sysfs interfaces Nam Tran
2025-04-06 12:08 ` Krzysztof Kozlowski
2025-04-10 16:25 ` Nam Tran
2025-04-05 18:32 ` [PATCH v4 4/5] docs: leds: Document TI LP5812 LED driver Nam Tran
2025-04-05 18:32 ` [PATCH v4 5/5] arm64: dts: Add LP5812 LED node for Raspberry Pi 4 Model B Nam Tran
2025-04-07 12:47 ` [PATCH v4 0/5] leds: add new LED driver for TI LP5812 Rob Herring (Arm)
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=eac877d0-2fd3-44cf-8917-910042cdcec9@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;
as well as URLs for NNTP newsgroup(s).