From: Lee Jones <lee@kernel.org>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: Pavel Machek <pavel@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Steffen Trumtrar <kernel@pengutronix.de>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] leds: lp5860: add enable-gpio
Date: Mon, 9 Mar 2026 18:22:36 +0000 [thread overview]
Message-ID: <20260309182236.GY183676@google.com> (raw)
In-Reply-To: <20260217-v6-19-topic-ti-lp5860-enable-gpio-v1-0-f5e8edeb5d74@pengutronix.de>
On Tue, 17 Feb 2026, Steffen Trumtrar wrote:
> The LP5860 can have the VIO_EN pin either be connected to VIO power
> supply or a GPIO.
>
> Add support for the pin to the devicetree binding and the driver.
>
> Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
> ---
> Steffen Trumtrar (2):
> dt-bindings: leds: lp5860: add enable-gpio
> leds: rgb: lp5860: add enable-gpio
>
> Documentation/devicetree/bindings/leds/leds-lp5860.yaml | 7 +++++++
> drivers/leds/rgb/leds-lp5860-core.c | 10 ++++++++++
> include/linux/platform_data/leds-lp5860.h | 1 +
> 3 files changed, 18 insertions(+)
> ---
> base-commit: 51455910fda1e5e315f604b7633f413116d4fa1f
> change-id: 20260217-v6-19-topic-ti-lp5860-enable-gpio-83c0652d34ad
> prerequisite-message-id: <20260217-v6-14-topic-ti-lp5860-v6-1-54a766d8b602@pengutronix.de>
> prerequisite-patch-id: 1d4485e2a6544fae1103cf9475f317773f206dc5
As you're probably already aware, the set does not apply.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2026-03-09 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 15:35 [PATCH 0/2] leds: lp5860: add enable-gpio Steffen Trumtrar
2026-02-17 15:35 ` [PATCH 1/2] dt-bindings: " Steffen Trumtrar
2026-02-17 17:54 ` Conor Dooley
2026-02-17 15:35 ` [PATCH 2/2] leds: rgb: " Steffen Trumtrar
2026-03-05 8:57 ` Steffen Trumtrar
2026-03-09 18:22 ` Lee Jones [this message]
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=20260309182236.GY183676@google.com \
--to=lee@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=robh@kernel.org \
--cc=s.trumtrar@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.