From: Daniel Mack <daniel.mack@holoplot.com>
To: linux-leds@vger.kernel.org
Cc: pavel@kernel.org, lee@kernel.org, robh@kernel.org,
devicetree@vger.kernel.org, Daniel Mack <daniel@zonque.org>
Subject: [PATCH v2 1/3] dt-bindings: leds: add issi,is31fl3293 to leds-is31fl32xx
Date: Fri, 14 Nov 2025 10:46:38 +0100 [thread overview]
Message-ID: <20251114094640.4096054-2-daniel.mack@holoplot.com> (raw)
In-Reply-To: <20251114094640.4096054-1-daniel.mack@holoplot.com>
From: Daniel Mack <daniel@zonque.org>
This variant supports 3 channels with 4096 brightness steps.
Signed-off-by: Daniel Mack <daniel@zonque.org>
---
Documentation/devicetree/bindings/leds/leds-is31fl32xx.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/leds/leds-is31fl32xx.txt b/Documentation/devicetree/bindings/leds/leds-is31fl32xx.txt
index 926c2117942c..7082ed186dd9 100644
--- a/Documentation/devicetree/bindings/leds/leds-is31fl32xx.txt
+++ b/Documentation/devicetree/bindings/leds/leds-is31fl32xx.txt
@@ -10,6 +10,7 @@ Required properties:
issi,is31fl3235
issi,is31fl3218
issi,is31fl3216
+ issi,is31fl3293
si-en,sn3218
si-en,sn3216
- reg: I2C slave address
--
2.51.1
next prev parent reply other threads:[~2025-11-14 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 9:46 [PATCH v2 0/3] leds: is31f132xx: add support for is31fl3293 Daniel Mack
2025-11-14 9:46 ` Daniel Mack [this message]
2025-11-14 17:53 ` [PATCH v2 1/3] dt-bindings: leds: add issi,is31fl3293 to leds-is31fl32xx Conor Dooley
2025-11-14 9:46 ` [PATCH v2 2/3] leds: is31f132xx: add support for is31fl3293 Daniel Mack
2025-11-14 9:46 ` [PATCH v2 3/3] leds: is31f132xx: re-order code to remove forward declarations Daniel Mack
2025-11-20 10:42 ` [PATCH v2 0/3] leds: is31f132xx: add support for is31fl3293 Lee Jones
2025-11-20 10:44 ` 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=20251114094640.4096054-2-daniel.mack@holoplot.com \
--to=daniel.mack@holoplot.com \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@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;
as well as URLs for NNTP newsgroup(s).