From: Nam Tran <trannamatk@gmail.com>
To: 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, Nam Tran <trannamatk@gmail.com>
Subject: [PATCH v5 5/5] arm64: dts: Add LP5812 LED node for Raspberry Pi 4 Model B
Date: Mon, 14 Apr 2025 21:57:42 +0700 [thread overview]
Message-ID: <20250414145742.35713-6-trannamatk@gmail.com> (raw)
In-Reply-To: <20250414145742.35713-1-trannamatk@gmail.com>
Add the LP5812 LED driver node to the Device Tree for Raspberry Pi 4 B.
This enables the LED connected to the LP5812 to be controlled via I2C.
Signed-off-by: Nam Tran <trannamatk@gmail.com>
---
.../arm/boot/dts/broadcom/bcm2711-rpi-4-b.dts | 60 +++++++++++++++++++
1 file changed, 60 insertions(+)
diff --git a/arch/arm/boot/dts/broadcom/bcm2711-rpi-4-b.dts b/arch/arm/boot/dts/broadcom/bcm2711-rpi-4-b.dts
index 353bb50ce542..0dec6ce44c6c 100644
--- a/arch/arm/boot/dts/broadcom/bcm2711-rpi-4-b.dts
+++ b/arch/arm/boot/dts/broadcom/bcm2711-rpi-4-b.dts
@@ -152,6 +152,66 @@ &hdmi1 {
status = "okay";
};
+&i2c1 {
+ #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";
+ };
+ led@1 {
+ reg = <0x1>;
+ chan-name = "a1";
+ };
+ led@2 {
+ reg = <0x2>;
+ chan-name = "a2";
+ };
+ led@3 {
+ reg = <0x3>;
+ chan-name = "b0";
+ };
+ led@4 {
+ reg = <0x4>;
+ chan-name = "b1";
+ };
+ led@5 {
+ reg = <0x5>;
+ chan-name = "b2";
+ };
+ led@6 {
+ reg = <0x6>;
+ chan-name = "c0";
+ };
+ led@7 {
+ reg = <0x7>;
+ chan-name = "c1";
+ };
+ led@8 {
+ reg = <0x8>;
+ chan-name = "c2";
+ };
+ led@9 {
+ reg = <0x9>;
+ chan-name = "d0";
+ };
+ led@a {
+ reg = <0xa>;
+ chan-name = "d1";
+ };
+ led@b {
+ reg = <0xb>;
+ chan-name = "d2";
+ };
+ };
+};
+
&led_act {
gpios = <&gpio 42 GPIO_ACTIVE_HIGH>;
};
--
2.25.1
next prev parent reply other threads:[~2025-04-14 14:58 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
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 ` Nam Tran [this message]
2025-04-14 15:10 ` [PATCH v5 5/5] arm64: dts: Add LP5812 LED node for Raspberry Pi 4 Model B 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=20250414145742.35713-6-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