[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260106-ltc3220-driver-v1-0-73601d6f1649@analog.com>
Date: Tue, 6 Jan 2026 13:27:06 +0800
From: Edelweise Escala <edelweise.escala@...log.com>
To: Lee Jones <lee@...nel.org>, Pavel Machek <pavel@...nel.org>,
Rob Herring
<robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley
<conor+dt@...nel.org>
CC: <linux-leds@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
Edelweise Escala
<edelweise.escala@...log.com>
Subject: [PATCH 0/2] Add Support for LTC3220 18 Channel LED Driver
The LTC3220/LTC3220-1 is a multi-display LED driver, which contains a high-efficiency,
low-noise charge pump to provide power to up to 18 LED current sources.
The LEDs are individually configurable to 64-step linear brightness control,
blinking and gradation control via 2-wire I2C interface.
The blinking and gradation configuration is shared across all LED.
LTC3220 has a quick write function which allows changing the brightness
on all LEDS simultaneously when the brightness is changed on led 1.
For this we made quick write a device property which user can set on the device tree.
We would like to know if this approach is alright?
Another way we might want to know is, is it alright to just make a virtual led for the quick write function.
Changing brightness on the virtual led will change the brightness for all.
Signed-off-by: Edelweise Escala <edelweise.escala@...log.com>
---
Edelweise Escala (2):
dt-bindings: leds: Document LTC3220 18 channel LED Driver
leds: ltc3220: add driver
.../devicetree/bindings/leds/leds-ltc3220.yaml | 131 ++++++
MAINTAINERS | 8 +
drivers/leds/Kconfig | 10 +
drivers/leds/Makefile | 1 +
drivers/leds/leds-ltc3220.c | 465 +++++++++++++++++++++
5 files changed, 615 insertions(+)
---
base-commit: 8856d7fe1758937ac528770f552ec58c388c255b
change-id: 20260106-ltc3220-driver-f9ab6cc9d1e4
Best regards,
--
Edelweise Escala <edelweise.escala@...log.com>
Powered by blists - more mailing lists