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 v6 0/5] leds: add new LED driver for TI LP5812
Date: Sun, 20 Apr 2025 01:43:28 +0700 [thread overview]
Message-ID: <20250419184333.56617-1-trannamatk@gmail.com> (raw)
This patch series adds support for the TI/National Semiconductor LP5812
4x3 matrix RGB LED driver. The driver supports features such as autonomous
animation and time-cross-multiplexing (TCM) for dynamic LED effects.
Signed-off-by: Nam Tran <trannamatk@gmail.com>
---
Changes in v6:
- Add `vcc-supply` property to describe the LP5812 power supply.
- Remove `chan-name` property and entire LED subnodes, as they are not needed.
- Update LP5812 LED driver node to Raspberry Pi 4 B Device Tree, based on updated binding.
- Link to v5: https://lore.kernel.org/linux-leds/20250414145742.35713-1-trannamatk@gmail.com/
Changes in v5:
- Rebase on v6.15-rc2
- Removed unused functions (lp5812_dump_regs, lp5812_update_bit).
- Address Krzysztof's review comments
- Link to v4: https://lore.kernel.org/linux-leds/20250405183246.198568-1-trannamatk@gmail.com/
---
Nam Tran (5):
dt-bindings: leds: add TI/National Semiconductor LP5812 LED Driver
leds: add TI/National Semiconductor LP5812 LED Driver
docs: ABI: Document LP5812 LED sysfs interfaces
docs: leds: Document TI LP5812 LED driver
arm64: dts: Add LP5812 LED node for Raspberry Pi 4 Model B
.../ABI/testing/sysfs-bus-i2c-devices-lp5812 | 144 +
.../devicetree/bindings/leds/ti,lp5812.yaml | 46 +
Documentation/leds/leds-lp5812.rst | 79 +
MAINTAINERS | 12 +
.../arm/boot/dts/broadcom/bcm2711-rpi-4-b.dts | 10 +
drivers/leds/Kconfig | 16 +
drivers/leds/Makefile | 1 +
drivers/leds/leds-lp5812.c | 2797 +++++++++++++++++
drivers/leds/leds-lp5812.h | 350 +++
9 files changed, 3455 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-bus-i2c-devices-lp5812
create mode 100644 Documentation/devicetree/bindings/leds/ti,lp5812.yaml
create mode 100644 Documentation/leds/leds-lp5812.rst
create mode 100644 drivers/leds/leds-lp5812.c
create mode 100644 drivers/leds/leds-lp5812.h
base-commit: 8ffd015db85fea3e15a77027fda6c02ced4d2444
--
2.25.1
next reply other threads:[~2025-04-19 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-19 18:43 Nam Tran [this message]
2025-04-19 18:43 ` [PATCH v6 1/5] dt-bindings: leds: add TI/National Semiconductor LP5812 LED Driver Nam Tran
2025-04-22 8:35 ` Krzysztof Kozlowski
2025-04-19 18:43 ` [PATCH v6 2/5] " Nam Tran
2025-04-20 13:29 ` Christophe JAILLET
2025-04-21 2:21 ` Nam Tran
2025-04-19 18:43 ` [PATCH v6 3/5] docs: ABI: Document LP5812 LED sysfs interfaces Nam Tran
2025-04-19 18:43 ` [PATCH v6 4/5] docs: leds: Document TI LP5812 LED driver Nam Tran
2025-04-19 18:43 ` [PATCH v6 5/5] arm64: dts: Add LP5812 LED node for Raspberry Pi 4 Model B 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=20250419184333.56617-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