From: "Jérôme de Bretagne" <jerome.debretagne@gmail.com>
To: sashiko-reviews@lists.linux.dev
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org,
Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH 02/11] arm64: dts: qcom: sc8280xp-arcata: Enable backlight
Date: Thu, 21 May 2026 00:01:31 +0200 [thread overview]
Message-ID: <ec232a52-795b-4f32-bcb4-2b6e5f8fc928@gmail.com> (raw)
In-Reply-To: <20260520165709.E485C1F00893@smtp.kernel.org>
On 5/20/26 18:57, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [High] The eDP backlight regulator (`vreg_edp_bl`) is mapped to the wrong PMIC for its enable GPIO, directly contradicting the hardware findings documented in the commit message.
> --
>
> commit 5bb21a2e354ddc1fbe2cb4a72c610f631fc3961f
> Author: Jérôme de Bretagne <jerome.debretagne@gmail.com>
>
> arm64: dts: qcom: sc8280xp-arcata: Enable backlight
>
> This commit adds backlight nodes and enables the backlight so that it can be
> controlled with the buttons on Surface Pro Type Cover keyboards. The nodes
> are similar to the ThinkPad X13s but use a different enable GPIO for the
> vreg_edp_bl node.
>
>> diff --git a/arch/arm64/boot/dts/qcom/sc8280xp-microsoft-arcata.dts b/arch/arm64/boot/dts/qcom/sc8280xp-microsoft-arcata.dts
>> index f2b4470d4407f..14287092fb07e 100644
>> --- a/arch/arm64/boot/dts/qcom/sc8280xp-microsoft-arcata.dts
>> +++ b/arch/arm64/boot/dts/qcom/sc8280xp-microsoft-arcata.dts
> [ ... ]
>> @@ -127,6 +137,22 @@ pmic_glink_con1_sbu: endpoint {
>> };
>> };
>>
>> + vreg_edp_bl: regulator-edp-bl {
>> + compatible = "regulator-fixed";
>> +
>> + regulator-name = "VREG_EDP_BL";
>> + regulator-min-microvolt = <3600000>;
>> + regulator-max-microvolt = <3600000>;
>> +
>> + gpio = <&pmc8280c_gpios 6 GPIO_ACTIVE_HIGH>;
>
> [Severity: High]
> Does this map to the correct PMIC for the enable GPIO?
>
> The commit message explicitly states that the hardware match for the backlight
> enable GPIO was found at platform/c440000.spmi:pmic@3:gpio@8800 (which is
> gpio6).
>
> According to sc8280xp-pmics.dtsi, pmic@3 corresponds to the pmc8280_2 PMIC and
> its pmc8280_2_gpios controller.
>
> However, the patch configures the regulator and pinctrl to use pmc8280c_gpios,
> which is physically mapped to pmic@2.
>
> Will this result in toggling the wrong physical pin on pmic@2 instead of
> enabling the eDP backlight?
>
>> + enable-active-high;
>> +
>> + pinctrl-0 = <&edp_bl_reg_en>;
>> + pinctrl-names = "default";
>> +
>> + regulator-boot-on;
>> + };
>
I was skeptical at first but upon review I've tried the following patch:
diff --git a/arch/arm64/boot/dts/qcom/sc8280xp-microsoft-arcata.dts
b/arch/arm64/boot/dts/qcom/sc8280xp-microsoft-arcata.dts
index f938e68c69ea..82e0a01276a8 100644
--- a/arch/arm64/boot/dts/qcom/sc8280xp-microsoft-arcata.dts
+++ b/arch/arm64/boot/dts/qcom/sc8280xp-microsoft-arcata.dts
@@ -198,7 +198,7 @@ vreg_edp_bl: regulator-edp-bl {
regulator-min-microvolt = <3600000>;
regulator-max-microvolt = <3600000>;
- gpio = <&pmc8280c_gpios 6 GPIO_ACTIVE_HIGH>;
+ gpio = <&pmc8280_2_gpios 6 GPIO_ACTIVE_HIGH>;
enable-active-high;
pinctrl-0 = <&edp_bl_reg_en>;
@@ -1050,6 +1050,11 @@ vol_up_n: vol-up-n-state {
};
&pmc8280_2_gpios {
+ edp_bl_reg_en: edp-bl-reg-en-state {
+ pins = "gpio6";
+ function = "normal";
+ };
+
wwan_sw_en: wwan-sw-en-state {
pins = "gpio1";
function = "normal";
@@ -1061,11 +1066,6 @@ edp_bl_pwm: edp-bl-pwm-state {
pins = "gpio8";
function = "func1";
};
-
- edp_bl_reg_en: edp-bl-reg-en-state {
- pins = "gpio6";
- function = "normal";
- };
};
&pmr735a_gpios {
and ... backlight still works! It can also be enabled/disabled with:
/sys/class/backlight/backlight/bl_power
as expected.
I have no clue why both gpio6 on pmc8280_2 and gpio6 on pmc8280c can
enable and disable the backlight. Is it a common scenario, Johan?
Anyway, if I follow my own investigation fully based on the X13s
reference and the properties of its backlight enable GPIO, I should
switch to pmc8280_2 to use the better match.
I will update this patch in v2.
Jérôme
next prev parent reply other threads:[~2026-05-20 22:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 16:40 [PATCH 00/11] Microsoft Surface Pro 9 5G update Jérôme de Bretagne via B4 Relay
2026-05-20 16:40 ` [PATCH 01/11] drm/panel: edp: Add LG LP129WT232166 panel Jérôme de Bretagne via B4 Relay
2026-05-20 16:40 ` [PATCH 02/11] arm64: dts: qcom: sc8280xp-arcata: Enable backlight Jérôme de Bretagne via B4 Relay
2026-05-20 16:57 ` sashiko-bot
2026-05-20 22:01 ` Jérôme de Bretagne [this message]
2026-05-20 22:26 ` Jérôme de Bretagne
2026-05-21 8:48 ` Konrad Dybcio
2026-05-20 16:40 ` [PATCH 03/11] arm64: dts: qcom: sc8280xp-arcata: Enable the eDP display Jérôme de Bretagne via B4 Relay
2026-05-20 17:04 ` sashiko-bot
2026-05-21 8:50 ` Konrad Dybcio
2026-05-20 16:40 ` [PATCH 04/11] arm64: dts: qcom: sc8280xp-arcata: add USB-C orientation GPIOs Jérôme de Bretagne via B4 Relay
2026-05-21 8:52 ` Konrad Dybcio
2026-05-20 16:40 ` [PATCH 05/11] arm64: dts: qcom: sc8280xp-arcata: Fix top USB-C DP alt mode Jérôme de Bretagne via B4 Relay
2026-05-21 8:53 ` Konrad Dybcio
2026-05-20 16:40 ` [PATCH 06/11] arm64: dts: qcom: sc8280xp-arcata: Enable 4-lane DP support Jérôme de Bretagne via B4 Relay
2026-05-20 16:40 ` [PATCH 07/11] arm64: dts: qcom: sc8280xp-arcata: Add volume up/down GPIO keys Jérôme de Bretagne via B4 Relay
2026-05-21 8:54 ` Konrad Dybcio
2026-05-20 16:40 ` [PATCH 08/11] arm64: dts: qcom: sc8280xp-arcata: Add lid switch Jérôme de Bretagne via B4 Relay
2026-05-21 8:54 ` Konrad Dybcio
2026-05-20 16:40 ` [PATCH 09/11] arm64: dts: qcom: sc8280xp-arcata: model the PMU of the on-board wcn6855 Jérôme de Bretagne via B4 Relay
2026-05-21 8:57 ` Konrad Dybcio
2026-05-20 16:40 ` [PATCH 10/11] arm64: dts: qcom: sc8280xp-arcata: Switch to uefi rtc offset Jérôme de Bretagne via B4 Relay
2026-05-21 8:57 ` Konrad Dybcio
2026-05-20 16:40 ` [PATCH 11/11] arm64: dts: qcom: sc8280xp-arcata: Drop duplicate DMIC supplies Jérôme de Bretagne via B4 Relay
2026-05-21 8:58 ` Konrad Dybcio
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=ec232a52-795b-4f32-bcb4-2b6e5f8fc928@gmail.com \
--to=jerome.debretagne@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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