From: Raymond Hackley <raymondhackley@protonmail.com>
To: open list <linux-kernel@vger.kernel.org>
Cc: Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Luca Weiss <luca@z3ntu.xyz>,
"open list : LED SUBSYSTEM" <linux-leds@vger.kernel.org>,
"open list : OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
~postmarketos/upstreaming@lists.sr.ht
Subject: [RESEND PATCH 2/2] leds: sgm3140: Add richtek,rt5033-led compatible
Date: Fri, 02 Jun 2023 13:38:12 +0000 [thread overview]
Message-ID: <20230602133726.260610-1-raymondhackley@protonmail.com> (raw)
In-Reply-To: <20230602133533.260502-1-raymondhackley@protonmail.com>
Richtek's rt5033-led has pin configurations similar to sgm3140.
Add it to the compatible list.
Signed-off-by: Raymond Hackley <raymondhackley@protonmail.com>
---
drivers/leds/flash/leds-sgm3140.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/leds/flash/leds-sgm3140.c b/drivers/leds/flash/leds-sgm3140.c
index d3a30ad94ac4..d3f50dca5136 100644
--- a/drivers/leds/flash/leds-sgm3140.c
+++ b/drivers/leds/flash/leds-sgm3140.c
@@ -291,6 +291,7 @@ static int sgm3140_remove(struct platform_device *pdev)
static const struct of_device_id sgm3140_dt_match[] = {
{ .compatible = "ocs,ocp8110" },
+ { .compatible = "richtek,rt5033-led" },
{ .compatible = "sgmicro,sgm3140" },
{ /* sentinel */ }
};
--
2.30.2
next prev parent reply other threads:[~2023-06-02 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 13:36 [RESEND PATCH 0/2] leds: sgm3140: Add richtek,rt5033-led compatible Raymond Hackley
2023-06-02 13:38 ` [RESEND PATCH 1/2] dt-bindings: leds: sgm3140: Document richtek,rt5033 compatible Raymond Hackley
2023-06-04 10:43 ` Krzysztof Kozlowski
2023-06-21 17:56 ` Raymond Hackley
2023-06-08 12:46 ` Lee Jones
2023-06-02 13:38 ` Raymond Hackley [this message]
2023-06-03 8:25 ` [RESEND PATCH 0/2] leds: sgm3140: Add richtek,rt5033-led compatible Luca Weiss
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=20230602133726.260610-1-raymondhackley@protonmail.com \
--to=raymondhackley@protonmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=pavel@ucw.cz \
--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).