From: Abel Vesa <abel.vesa@linaro.org>
To: Sebastian Reichel <sre@kernel.org>
Cc: 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>,
Johan Hovold <johan@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 1/2] arm64: dts: qcom: x1e78100-t14s: Add LCD variant with backlight support
Date: Sun, 9 Mar 2025 11:19:52 +0200 [thread overview]
Message-ID: <Z81dODU91zDPo/H5@linaro.org> (raw)
In-Reply-To: <lolqokpczxdscvgj6xdfyxblmle3csgzje3fgo4itzspgmeriy@7zzx7hg2zfks>
On 25-03-08 01:01:31, Sebastian Reichel wrote:
> Hi,
>
> On Thu, Mar 06, 2025 at 11:05:02AM +0200, Abel Vesa wrote:
> > Due to the fact that Lenovo Thinkpad T14s Gen6 is available with both
> > OLED and LCD, the backlight control differs HW-wise. For the LCD variant,
> > the panel's backlight is controlled via one of the PWMs provided by the
> > PMK8550 PMIC. For the OLED variant, the backlight is internal to the
> > panel and therefore it is not described in devicetree.
> >
> > For this reason, create a generic dtsi for the T14s by renaming the
> > existing dts. While at it, add a node name to panel and drop the enable
> > gpio and pinctrl properties from the panel node. Then add the LCD variant
> > dts file with the old name and describe all backlight related nodes.
> >
> > So the existing dts will now be used for LCD variant while for OLED new
> > dts will be added.
> >
> > Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> > ---
> > [...]
> > + backlight: backlight {
> > + compatible = "pwm-backlight";
> > + pwms = <&pmk8550_pwm 0 5000000>;
>
> I've tried this patch series together with the fix series [0], but
> without the duty cycle calculation change [1]. Instead I changed the
> period from 5000000 to 4266667. With that everything works as
> expected for me.
>
> [0] https://lore.kernel.org/all/20250305-leds-qcom-lpg-fix-max-pwm-on-hi-res-v4-0-bfe124a53a9f@linaro.org/
> [1] https://lore.kernel.org/all/20250303-leds-qcom-lpg-compute-pwm-value-using-period-v1-1-833e729e3da2@linaro.org/
Yes, I forgot to squash in the correct period.
The period should actually be 4266537. This is because the max PWM value
is actually BIT(resolution) - 1.
Will update in next version.
The [1] patch was basically NACKed by Uwe. It is not needed if we set
the period to 4266537 in DT.
>
> Greetings,
>
> -- Sebastian
next prev parent reply other threads:[~2025-03-09 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 9:05 [RFC 0/2] arm64: dts: qcom: x1e78100-t14s: Rework devicetree for LCD and OLED SKUs Abel Vesa
2025-03-06 9:05 ` [RFC 1/2] arm64: dts: qcom: x1e78100-t14s: Add LCD variant with backlight support Abel Vesa
2025-03-08 0:01 ` Sebastian Reichel
2025-03-09 9:19 ` Abel Vesa [this message]
2025-03-10 0:09 ` Sebastian Reichel
2025-03-06 9:05 ` [RFC 2/2] arm64: dts: qcom: x1e78100-t14s: Add OLED variant Abel Vesa
2025-03-09 20:28 ` Krzysztof Kozlowski
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=Z81dODU91zDPo/H5@linaro.org \
--to=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sre@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox