From: Vincent Knecht <vincent.knecht@mailoo.org>
To: Pavel Machek <pavel@ucw.cz>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Vincent Knecht <vincent.knecht@mailoo.org>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, hns@goldelico.com
Subject: [PATCH v3 3/6] leds: is31fl319x: Add missing si-en compatibles
Date: Tue, 5 Jul 2022 18:31:31 +0200 [thread overview]
Message-ID: <20220705163136.2278662-4-vincent.knecht@mailoo.org> (raw)
In-Reply-To: <20220705163136.2278662-1-vincent.knecht@mailoo.org>
Add si-en compatibles for all chip variants.
Signed-off-by: Vincent Knecht <vincent.knecht@mailoo.org>
---
drivers/leds/leds-is31fl319x.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/leds/leds-is31fl319x.c b/drivers/leds/leds-is31fl319x.c
index 4161b9dd7e48..0db5d4988131 100644
--- a/drivers/leds/leds-is31fl319x.c
+++ b/drivers/leds/leds-is31fl319x.c
@@ -102,6 +102,10 @@ static const struct of_device_id of_is31fl319x_match[] = {
{ .compatible = "issi,is31fl3193", .data = &is31fl3193_cdef, },
{ .compatible = "issi,is31fl3196", .data = &is31fl3196_cdef, },
{ .compatible = "issi,is31fl3199", .data = &is31fl3199_cdef, },
+ { .compatible = "si-en,sn3190", .data = &is31fl3190_cdef, },
+ { .compatible = "si-en,sn3191", .data = &is31fl3190_cdef, },
+ { .compatible = "si-en,sn3193", .data = &is31fl3193_cdef, },
+ { .compatible = "si-en,sn3196", .data = &is31fl3196_cdef, },
{ .compatible = "si-en,sn3199", .data = &is31fl3199_cdef, },
{ }
};
@@ -432,6 +436,10 @@ static const struct i2c_device_id is31fl319x_id[] = {
{ "is31fl3193" },
{ "is31fl3196" },
{ "is31fl3199" },
+ { "sn3190" },
+ { "sn3191" },
+ { "sn3193" },
+ { "sn3196" },
{ "sn3199" },
{},
};
--
2.35.3
next prev parent reply other threads:[~2022-07-05 16:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 16:31 [PATCH v3 0/6] leds: Fix/Add is31fl319{0,1,3} support Vincent Knecht
2022-07-05 16:31 ` [PATCH v3 1/6] dt-bindings: leds: Convert is31fl319x to dtschema Vincent Knecht
2022-07-05 16:31 ` [PATCH v3 2/6] dt-bindings: leds: is31fl319x: Document variants specificities Vincent Knecht
2022-07-05 16:31 ` Vincent Knecht [this message]
2022-07-05 16:31 ` [PATCH v3 4/6] leds: is31fl319x: Use non-wildcard names for vars, structs and defines Vincent Knecht
2022-07-05 18:47 ` Andy Shevchenko
2022-07-05 16:31 ` [PATCH v3 5/6] leds: is31fl319x: Move chipset-specific values in chipdef struct Vincent Knecht
2022-07-05 18:51 ` Andy Shevchenko
2022-07-05 16:31 ` [PATCH v3 6/6] leds: is31fl319x: Add support for is31fl319{0,1,3} chips Vincent Knecht
2022-07-05 18:56 ` Andy Shevchenko
2022-07-05 18:57 ` [PATCH v3 0/6] leds: Fix/Add is31fl319{0,1,3} support Andy Shevchenko
2022-07-09 9:51 ` Vincent Knecht
2022-07-11 21:39 ` Andy Shevchenko
2022-07-11 21:40 ` Andy Shevchenko
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=20220705163136.2278662-4-vincent.knecht@mailoo.org \
--to=vincent.knecht@mailoo.org \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).