From: Luke Macken <luke@phorex.org>
To: srinivas.kandagatla@oss.qualcomm.com
Cc: andersson@kernel.org, konradybcio@kernel.org,
abelvesa@kernel.org, lee@kernel.org, pavel@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Luke Macken <luke@phorex.org>
Subject: Re: [PATCH 0/4] Mahua T14s Gen 7 eDP backlight via PMK8850 LPG
Date: Fri, 16 Oct 2026 17:51:17 -0600 [thread overview]
Message-ID: <20261016235117.4060834-1-luke@phorex.org> (raw)
In-Reply-To: <20261015194732.64428-1-srinivas.kandagatla@oss.qualcomm.com>
Tested on a Lenovo ThinkPad T14s Gen 7 (22A7000VUS, BOE NE140WUM-N41 panel)
with linux-next next-20261015 plus this series: the backlight device
/sys/class/backlight/backlight is registered with max_brightness 4095 and
the brightness keys work.
Tested-by: Luke Macken <luke@phorex.org>
Two observations: the panel's DPCD advertises PWM-pin brightness control
only (0x701 = 0x83, 0x702 = 0x95, no AUX_SET_CAP), and the firmware leaves
the PMK8850 PWM channel at 0xe800 enabled with GPIO5 in func3, so the LPG
path matches what the hardware is set up for.
prev parent reply other threads:[~2026-10-16 23:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 19:47 Srinivas Kandagatla
2026-10-15 19:47 ` [PATCH 1/4] dt-bindings: leds: qcom-lpg: add qcom,pmk8850-pwm compatible Srinivas Kandagatla
2026-10-17 16:55 ` Krzysztof Kozlowski
2026-10-15 19:47 ` [PATCH 2/4] leds: rgb: " Srinivas Kandagatla
2026-10-19 14:34 ` Lee Jones
2026-10-20 6:14 ` Srinivas Kandagatla
2026-10-15 19:47 ` [PATCH 3/4] arm64: dts: qcom: pmk8850: add PWM node Srinivas Kandagatla
2026-10-16 8:53 ` Konrad Dybcio
2026-10-15 19:47 ` [PATCH 4/4] arm64: dts: qcom: mahua-t14s: wire backlight through pmk8850 pwm Srinivas Kandagatla
2026-10-16 8:50 ` Konrad Dybcio
2026-10-16 23:51 ` Luke Macken [this message]
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=20261016235117.4060834-1-luke@phorex.org \
--to=luke@phorex.org \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@oss.qualcomm.com \
/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
all inboxes | Powered by JetHome®