From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Pavel Machek" <pavel@ucw.cz>, <barnabas.czeman@mainlining.org>
Cc: "Bjorn Andersson" <andersson@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Stephan Gerhold" <stephan@gerhold.net>,
"Otto Pflüger" <otto.pflueger@abscue.de>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Lee Jones" <lee@kernel.org>, "Joerg Roedel" <joro@8bytes.org>,
"Will Deacon" <will@kernel.org>,
"Robin Murphy" <robin.murphy@arm.com>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Sean Paul" <sean@poorly.run>,
"Abhinav Kumar" <quic_abhinavk@quicinc.com>,
"Marijn Suijten" <marijn.suijten@somainline.org>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Dmitry Baryshkov" <lumag@kernel.org>,
"Adam Skladowski" <a_skl39@protonmail.com>,
"Sireesh Kodali" <sireeshkodali@protonmail.com>,
"Rob Clark" <robin.clark@oss.qualcomm.com>,
"Abhinav Kumar" <abhinav.kumar@linux.dev>,
"Jessica Zhang" <jessica.zhang@oss.qualcomm.com>,
"Srinivas Kandagatla" <srini@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, iommu@lists.linux.dev,
dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht, linux@mainlining.org,
"Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v7 6/6] arm64: dts: qcom: Add Xiaomi Redmi 3S
Date: Tue, 23 Sep 2025 11:55:41 +0200 [thread overview]
Message-ID: <DD038IVOWESM.24X3EZZXH3UE@fairphone.com> (raw)
In-Reply-To: <aNJKniJ46YuUsbQ+@duo.ucw.cz>
Hi Pavel and Barnabas,
On Tue Sep 23, 2025 at 9:22 AM CEST, Pavel Machek wrote:
> Hi!
>> > Hi!
>> >
>> > > + led-controller@45 {
>> > > + compatible = "awinic,aw2013";
>> > > + reg = <0x45>;
>> > > + #address-cells = <1>;
>> > > + #size-cells = <0>;
>> > > +
>> > > + vcc-supply = <&pm8937_l10>;
>> > > + vio-supply = <&pm8937_l5>;
>> > > +
>> > > + led@0 {
>> > > + reg = <0>;
>> > > + function = LED_FUNCTION_STATUS;
>> > > + led-max-microamp = <5000>;
>> > > + color = <LED_COLOR_ID_RED>;
>> > > + };
>> > > +
>> > > + led@1 {
>> > > + reg = <1>;
>> > > + function = LED_FUNCTION_STATUS;
>> > > + led-max-microamp = <5000>;
>> > > + color = <LED_COLOR_ID_GREEN>;
>> > > + };
>> > > +
>> > > + led@2 {
>> > > + reg = <2>;
>> > > + function = LED_FUNCTION_STATUS;
>> > > + led-max-microamp = <5000>;
>> > > + color = <LED_COLOR_ID_BLUE>;
>> > > + };
>> > > + };
>> > > +};
>> >
>> > That's single, 3-color LED, right? Please see LED multicolor support.
>> As far as i know aw2013 driver does not have multicolor support.
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/leds/leds-aw2013.yaml
>
> I believe that needs to be fixed before more bugs are added on top to
> work around that problem...
>
> ...and before that bug is cemented in the ABI.
Honestly I don't think it's reasonable to expect people contributing dts
to then first start patching existing LED drivers and adding support for
x y or z to it, and block dts addition on that.
At least in postmarketOS the user space components we have (e.g.
feedbackd) detect the LED things (and most others) automatically since
various devices have various different setups. So once/if aw2013 gets
multicolor support, the dts can be updated without problems.
Sure, maybe today changing something on the N900 which would change
sysfs paths is not the best idea because people will probably have 10+
years of random shell scripts lying around, but nowadays we usually have
better ways of abstraction that can handle that.
Regards
Luca
>
> Best regards,
> Pavel
next prev parent reply other threads:[~2025-09-23 9:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 22:38 [PATCH v7 0/6] Initial support of MSM8937 and Xiaomi Redmi 3S Barnabás Czémán
2025-08-30 22:38 ` [PATCH v7 1/6] dt-bindings: clock: qcom: Add MSM8937 Global Clock Controller Barnabás Czémán
2025-08-30 22:38 ` [PATCH v7 2/6] clk: qcom: gcc: Add support for Global Clock controller found on MSM8937 Barnabás Czémán
2025-08-30 22:38 ` [PATCH v7 3/6] dt-bindings: display/msm/gpu: describe A505 clocks Barnabás Czémán
2025-08-30 22:38 ` [PATCH v7 4/6] arm64: dts: qcom: Add initial support for MSM8937 Barnabás Czémán
2025-08-31 10:00 ` Dmitry Baryshkov
2025-08-30 22:38 ` [PATCH v7 5/6] dt-bindings: arm: qcom: Add Xiaomi Redmi 3S Barnabás Czémán
2025-08-30 22:38 ` [PATCH v7 6/6] arm64: dts: " Barnabás Czémán
2025-09-22 17:45 ` Pavel Machek
2025-09-22 18:33 ` barnabas.czeman
2025-09-23 7:22 ` Pavel Machek
2025-09-23 9:55 ` Luca Weiss [this message]
2025-10-22 11:23 ` Pavel Machek
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=DD038IVOWESM.24X3EZZXH3UE@fairphone.com \
--to=luca.weiss@fairphone.com \
--cc=a_skl39@protonmail.com \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=barnabas.czeman@mainlining.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=jessica.zhang@oss.qualcomm.com \
--cc=joro@8bytes.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@mainlining.org \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=otto.pflueger@abscue.de \
--cc=pavel@ucw.cz \
--cc=phone-devel@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robh@kernel.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=robin.murphy@arm.com \
--cc=sboyd@kernel.org \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=sireeshkodali@protonmail.com \
--cc=srini@kernel.org \
--cc=stephan@gerhold.net \
--cc=tzimmermann@suse.de \
--cc=will@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