From: Pavel Machek <pavel@ucw.cz>
To: Alexandre Messier <alex@me.ssier.org>
Cc: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Luca Weiss <luca@lucaweiss.eu>,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] ARM: dts: qcom: msm8974pro-htc-m8: add status LEDs
Date: Mon, 24 Nov 2025 18:13:53 +0100 [thread overview]
Message-ID: <aSSSUahMBR8Wujni@duo.ucw.cz> (raw)
In-Reply-To: <77efe2a2-ee81-4096-9145-a76e35954e84@me.ssier.org>
[-- Attachment #1: Type: text/plain, Size: 2273 bytes --]
Hi!
> >>> Do they form a single notification led, or are they supposed
> >>> to act separately?
> >>
> >> Good point, I had to check the phone user manual to confirm. Indeed, it is
> >> referred to as a one logical notification LED. It also mentions the color can
> >> be either green or orange, it does not mention using the combined color of
> >> the two LEDs.
> >>
> >> So I would say they are supposed to act separately.
> >>
> >> Hope this answers your question, and let me know if more details are needed.
> >>
> >> BTW: I will be sending a V2 to update the color name, since the user
> >> manual says the color is orange, not amber.
> >
> > Let's describe it as a single LED then:
> >
> > multi-led {
> > color = <LED_COLOR_ID_MULTI>; // notice it's not RGB
> > function = LED_FUNCTION_STATUS;
> >
> > #address-cells = <1>;
> > #size-cells = <0>;
> >
> > led@6 {
> > reg = <6>;
> > color = <LED_COLOR_ID_GREEN>;
> > };
> >
> > led@7 {
> > reg = <7>;
> > color = <LED_COLOR_ID_ORANGE>;
> > };
> > };
>
> Using multi-led is fine for me.
>
> But currently, the "qcom-lpg" driver doesn't support LED_COLOR_ID_MULTI, only
> LED_COLOR_ID_RGB. Adding support for LED_COLOR_ID_MULTI is trivial, I tested it
> and it works.
>
> Or I can also use the "leds-group-multicolor" driver, using the two individual
> LEDs. I also tested this method and it works.
>
> >
> > + Pavel the LED maintainer, please take a look if you think it makes sense
>
> If Pavel agrees using multi-led makes sense, I think the first option is the
> best. I will separate the LED patch into a new series, along with the change to
> the qcom-lpg driver to support LED_COLOR_ID_MULTI.
I see nothing horribly wrong here (and am late to the party). ID_MULTI
leds are pretty uncommon for phones, but if that's what you have...
Anyway:
LED SUBSYSTEM
M: Lee Jones <lee@kernel.org>
M: Pavel Machek <pavel@kernel.org>
L: linux-leds@vger.kernel.org
Best regards,
Pavel
--
I don't work for Nazis and criminals, and neither should you.
Boycott Putin, Trump, Netanyahu and Musk!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2025-11-24 17:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 5:55 [PATCH 0/4] Describe more hardware of the HTC One (M8) Alexandre Messier via B4 Relay
2025-10-07 5:55 ` [PATCH 1/4] ARM: dts: qcom: msm8974pro-htc-m8: add status LEDs Alexandre Messier via B4 Relay
2025-10-07 10:03 ` Konrad Dybcio
2025-10-12 6:03 ` Alexandre Messier
2025-10-20 12:02 ` Konrad Dybcio
2025-10-22 7:00 ` Alexandre Messier
2025-11-24 17:13 ` Pavel Machek [this message]
2025-10-07 5:55 ` [PATCH 2/4] ARM: dts: qcom: msm8974pro-htc-m8: add NFC support Alexandre Messier via B4 Relay
2025-10-07 10:03 ` Konrad Dybcio
2025-10-07 5:55 ` [PATCH 3/4] ARM: dts: qcom: msm8974pro-htc-m8: add Bluetooth pins Alexandre Messier via B4 Relay
2025-10-07 10:05 ` Konrad Dybcio
2025-10-07 5:55 ` [PATCH 4/4] ARM: dts: qcom: msm8974pro-htc-m8: add touchscreen Alexandre Messier via B4 Relay
2025-10-07 10:04 ` Konrad Dybcio
2025-10-09 5:50 ` Alexandre Messier
2025-10-09 9:30 ` Konrad Dybcio
2025-10-12 6:06 ` Alexandre Messier
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=aSSSUahMBR8Wujni@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=alex@me.ssier.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@lucaweiss.eu \
--cc=phone-devel@vger.kernel.org \
--cc=robh@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).