From: barnabas.czeman@mainlining.org
To: Daniel Thompson <danielt@kernel.org>
Cc: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Lee Jones <lee@kernel.org>, Jingoo Han <jingoohan1@gmail.com>,
Pavel Machek <pavel@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Kiran Gunda <quic_kgunda@quicinc.com>,
Helge Deller <deller@gmx.de>, Luca Weiss <luca@lucaweiss.eu>,
Konrad Dybcio <konradybcio@kernel.org>,
Eugene Lepshy <fekz115@gmail.com>,
Gianluca Boiano <morf3089@gmail.com>,
Alejandro Tafalla <atafalla@dnyon.com>,
dri-devel@lists.freedesktop.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2 2/7] backlight: qcom-wled: Support ovp values for PMI8994
Date: Fri, 09 Jan 2026 16:42:57 +0100 [thread overview]
Message-ID: <00d0c357d31463272d786bcc9abfe295@mainlining.org> (raw)
In-Reply-To: <aWEDr3O9T7bASnj9@aspen.lan>
On 2026-01-09 14:33, Daniel Thompson wrote:
> On Fri, Jan 09, 2026 at 12:09:11PM +0100, Konrad Dybcio wrote:
>> On 1/9/26 7:36 AM, barnabas.czeman@mainlining.org wrote:
>> > On 2026-01-08 12:28, Daniel Thompson wrote:
>> >> On Thu, Jan 08, 2026 at 04:43:20AM +0100, Barnabás Czémán wrote:
>> >>> WLED4 found in PMI8994 supports different ovp values.
>> >>>
>> >>> Fixes: 6fc632d3e3e0 ("video: backlight: qcom-wled: Add PMI8994 compatible")
>> >>> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>> >>> Signed-off-by: Barnabás Czémán <barnabas.czeman@mainlining.org>
>> >>> ---
>> >>> drivers/video/backlight/qcom-wled.c | 41 +++++++++++++++++++++++++++++++++++--
>> >>> 1 file changed, 39 insertions(+), 2 deletions(-)
>> >>>
>> >>> diff --git a/drivers/video/backlight/qcom-wled.c b/drivers/video/backlight/qcom-wled.c
>> >>> index a63bb42c8f8b..5decbd39b789 100644
>> >>> --- a/drivers/video/backlight/qcom-wled.c
>> >>> +++ b/drivers/video/backlight/qcom-wled.c
>> >>> @@ -1244,6 +1244,15 @@ static const struct wled_var_cfg wled4_ovp_cfg = {
>> >>> .size = ARRAY_SIZE(wled4_ovp_values),
>> >>> };
>> >>>
>> >>> +static const u32 pmi8994_wled_ovp_values[] = {
>> >>> + 31000, 29500, 19400, 17800,
>> >>> +};
>> >>> +
>> >>> +static const struct wled_var_cfg pmi8994_wled_ovp_cfg = {
>> >>> + .values = pmi8994_wled_ovp_values,
>> >>> + .size = ARRAY_SIZE(pmi8994_wled_ovp_values),
>> >>> +};
>> >>> +
>> >>
>> >> Do these *have* to be named after one of the two PMICs that implement
>> >> this OVP range.
>> >>
>> >> Would something like wled4_alternative_ovp_values[] (and the same
>> >> throughout the patch) be more descriptive?
>> > I don't know. I don't like the PMIC naming either but at least it
>> > descriptive about wich PMIC is needing these values.
>
> It's the descriptive but wrong element I dislike (pmi8994_wled_ovp_cfg
> is used by pmi8550).
No, pmi8950 is using pmi8994_wled_opts struct what is using
pmi8994_wled_ovp_cfg.
>
> I know these things crop up for "historical reasons" when is appears in
> the same patchset I have to question the naming.
>
>
>> > I think PMIC naming would be fine if compatibles what representing the
>> > same configurations would be deprecated and used as a fallback compatbile
>> > style.
>> > I mean we could kept the first added compatible for a configuration.
>> > Maybe they should be named diferently i don't know if WLEDs have subversion.
>>
>> Every PMIC peripheral is versioned.
>>
>> WLED has separate versioning for the digital and analog parts:
>>
>> PMIC ANA DIG
>> ---------------------------
>> PMI8937 2.0 1.0 (also needs the quirk)
>> PMI8950 2.0 1.0
>> PMI8994 2.0 1.0
>> PMI8996 2.1 1.0
>> PMI8998 3.1 3.0
>> PM660L 4.1 4.0
>>
>> I don't know for sure if "PMIC4 with WLED ANA/DIG 3.x" a good
>> discriminant though..
>
> Peronally I'd prefer that to making them all use pmi8994 structures.
> It's a much better link back to the docs (at least for those with the
> power to read them ;-) ).
>
>
> Daniel.
next prev parent reply other threads:[~2026-01-09 15:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 3:43 [PATCH v2 0/7] Fix PMI8950 WLED ovp values and more Barnabás Czémán
2026-01-08 3:43 ` [PATCH v2 1/7] dt-bindings: backlight: qcom-wled: Document ovp values for PMI8994 Barnabás Czémán
2026-01-08 8:54 ` Konrad Dybcio
2026-01-08 9:17 ` barnabas.czeman
2026-01-08 9:22 ` Konrad Dybcio
2026-01-08 9:30 ` barnabas.czeman
2026-01-08 9:21 ` Konrad Dybcio
2026-01-08 10:09 ` Krzysztof Kozlowski
2026-01-08 3:43 ` [PATCH v2 2/7] backlight: qcom-wled: Support " Barnabás Czémán
2026-01-08 8:55 ` Konrad Dybcio
2026-01-08 9:22 ` Konrad Dybcio
2026-01-08 11:28 ` Daniel Thompson
2026-01-09 6:36 ` barnabas.czeman
2026-01-09 11:09 ` Konrad Dybcio
2026-01-09 13:33 ` Daniel Thompson
2026-01-09 15:42 ` barnabas.czeman [this message]
2026-01-09 15:45 ` barnabas.czeman
2026-01-08 3:43 ` [PATCH v2 3/7] dt-bindings: backlight: qcom-wled: Document ovp values for PMI8950 Barnabás Czémán
2026-01-08 9:22 ` Konrad Dybcio
2026-01-08 10:17 ` Krzysztof Kozlowski
2026-01-08 3:43 ` [PATCH v2 4/7] backlight: qcom-wled: Fix " Barnabás Czémán
2026-01-08 9:22 ` Konrad Dybcio
2026-01-08 3:43 ` [PATCH v2 5/7] arm64: dts: qcom: msm8953-xiaomi-vince: correct wled ovp value Barnabás Czémán
2026-01-08 3:43 ` [PATCH v2 6/7] arm64: dts: qcom: msm8937-xiaomi-land: " Barnabás Czémán
2026-01-08 3:43 ` [PATCH v2 7/7] arm64: dts: qcom: msm8953-xiaomi-daisy: fix backlight Barnabás Czémán
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=00d0c357d31463272d786bcc9abfe295@mainlining.org \
--to=barnabas.czeman@mainlining.org \
--cc=andersson@kernel.org \
--cc=atafalla@dnyon.com \
--cc=conor+dt@kernel.org \
--cc=danielt@kernel.org \
--cc=deller@gmx.de \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fekz115@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=luca@lucaweiss.eu \
--cc=morf3089@gmail.com \
--cc=pavel@kernel.org \
--cc=quic_kgunda@quicinc.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.