From: Lee Jones <lee@kernel.org>
To: Jan Carlo Roleda <jancarlo.roleda@analog.com>
Cc: "Pavel Machek" <pavel@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v13 0/2] Add support for LTC3208 multi-display driver
Date: Tue, 22 Sep 2026 12:14:17 +0100 [thread overview]
Message-ID: <20260922111417.GA3277918@google.com> (raw)
In-Reply-To: <20260911-upstream-ltc3208-v13-0-fc9aa3758b55@analog.com>
On Fri, 11 Sep 2026, Jan Carlo Roleda wrote:
> 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>
I don't think you're based off of the correct tree.
Looks like you have patches in your base that aren't in the LEDs tree.
Please rebase and send as a [RESEND].
--
Lee Jones
next prev parent reply other threads:[~2026-09-22 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 0:01 [PATCH v13 0/2] Add support for LTC3208 multi-display driver Jan Carlo Roleda
2026-09-11 0:01 ` [PATCH v13 1/2] dt-bindings: leds: Document LTC3208 Multidisplay LED Driver Jan Carlo Roleda
2026-09-11 0:08 ` sashiko-bot
2026-09-11 0:01 ` [PATCH v13 2/2] leds: ltc3208: Add driver for " Jan Carlo Roleda
2026-09-11 0:07 ` sashiko-bot
2026-09-22 11:14 ` Lee Jones [this message]
2026-09-23 7:38 ` [PATCH v13 0/2] Add support for LTC3208 multi-display driver Lee Jones
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=20260922111417.GA3277918@google.com \
--to=lee@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jancarlo.roleda@analog.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@baylibre.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