From: Jan Carlo Roleda <jancarlo.roleda@analog.com>
To: Lee Jones <lee@kernel.org>, Pavel Machek <pavel@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-leds@vger.kernel.org>,
<devicetree@vger.kernel.org>,
Jan Carlo Roleda <jancarlo.roleda@analog.com>
Subject: [PATCH 0/3] Add support for LTC3208 multi-display driver
Date: Wed, 18 Mar 2026 14:59:19 +0800 [thread overview]
Message-ID: <20260318-upstream-ltc3208-v1-0-015f1f1e9065@analog.com> (raw)
The LTC3208 is a multi-display LED driver, using a high-efficiency, low
noise charge pump to provide power to 5 channels (MAIN, SUB, RGB, CAM,
AUX). Current for each LED is controlled by the I2C serial interface.
Four AUX current sources can be independently assigned via the I2C port
to the CAM, SUB, MAIN, or AUX DAC controlled displays
Signed-off-by: Jan Carlo Roleda <jancarlo.roleda@analog.com>
---
Jan Carlo Roleda (3):
Add Maintainers to LTC3208 LED Driver
leds: ltc3208: add driver
dt-bindings: leds: Document LTC3208 Multidisplay LED Driver
.../devicetree/bindings/leds/adi,ltc3208.yaml | 159 +++++++++++
MAINTAINERS | 8 +
drivers/leds/Kconfig | 11 +
drivers/leds/Makefile | 1 +
drivers/leds/leds-ltc3208.c | 298 +++++++++++++++++++++
5 files changed, 477 insertions(+)
---
base-commit: e68f95a51d1a8c1594b536c4d495cbea38d47561
change-id: 20260318-upstream-ltc3208-7cc8968bf69e
Best regards,
--
Jan Carlo Roleda <jancarlo.roleda@analog.com>
next reply other threads:[~2026-03-18 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 6:59 Jan Carlo Roleda [this message]
2026-03-18 6:59 ` [PATCH 1/3] Add Maintainers to LTC3208 LED Driver Jan Carlo Roleda
2026-03-18 6:59 ` [PATCH 2/3] leds: ltc3208: add driver Jan Carlo Roleda
2026-03-19 15:53 ` Dan Carpenter
2026-03-18 6:59 ` [PATCH 3/3] dt-bindings: leds: Document LTC3208 Multidisplay LED Driver Jan Carlo Roleda
2026-03-18 8:30 ` 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=20260318-upstream-ltc3208-v1-0-015f1f1e9065@analog.com \
--to=jancarlo.roleda@analog.com \
--cc=conor+dt@kernel.org \
--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
all inboxes | Powered by JetHome®