Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Nabige Aala" <nabige.aala@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 3/4] arm64: dts: qcom: shikra-cqm-evk: Enable display and add ili7807s panel
Date: Wed, 16 Sep 2026 09:19:13 +0000	[thread overview]
Message-ID: <20260916091913.8F51F1F0089A@smtp.kernel.org> (raw)
In-Reply-To: <20260916-shikra-dt-changes-v4-3-d5d5c3ffe070@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dts: backlight enable GPIO permanently asserted via pinctrl
--

commit 00c4e0f47a97a648f49ab088ecacedb0603403a5
Author: Arpit Saini <arpit.saini@oss.qualcomm.com>

arm64: dts: qcom: shikra-cqm-evk: Enable display and add ili7807s panel

This commit enables the Shikra MDSS display subsystem on the Qualcomm Shikra
CQM EVK board and adds the DLC0697 MIPI DSI display panel node. It also
pins pm4125_l5 to 1.232V for DSI PHY PLL stability.

> diff --git a/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts b/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts
> index b112b21b1d79b..d9a0f32ce8d3b 100644
> --- a/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts
> +++ b/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts
[ ... ]
> +&mdss_dsi0 {
> +	vdda-supply = <&pm4125_l5>;
> +
> +	status = "okay";
> +
> +	panel@0 {
> +		compatible = "dlc,dlc0697", "ilitek,ili7807s";
> +		reg = <0>;
> +
> +		reset-gpios = <&tlmm 3 GPIO_ACTIVE_LOW>;
> +
> +		vddi-supply = <&pm4125_l15>;
> +		avdd-supply = <&vreg_disp_p>;
> +		avee-supply = <&vreg_disp_n>;
> +
> +		pinctrl-0 = <&panel_rst_n &panel_te_pin &panel_bl_en>;

[Severity: Medium]
Does mapping panel_bl_en in the default pinctrl state bypass the display
power management sequence?

The device core automatically applies this default state before calling the
panel's probe function. Since the panel driver (panel-ilitek-ili7807s) does
not natively acquire this GPIO nor implement runtime power management (PM),
the driver core will not switch to the sleep pinctrl state during DRM
unprepare (blanking).

> +		pinctrl-1 = <&panel_rst_n_suspend &panel_bl_en_suspend>;
> +		pinctrl-names = "default", "sleep";
> +
> +		port {
> +			panel_in: endpoint {
> +				remote-endpoint = <&mdss_dsi0_out>;
> +			};
> +		};
> +	};
> +};
[ ... ]
> +&tlmm {
[ ... ]
> +	panel_bl_en: panel-bl-en-state {
> +		pins = "gpio91";
> +		function = "gpio";
> +		drive-strength = <2>;
> +		bias-disable;
> +		output-high;
> +	};

[Severity: Medium]
Will this output-high configuration cause the backlight to remain permanently
powered on while the system is awake? 

Because the panel driver does not toggle this via runtime PM, this could 
result in a glowing black screen when the display is conceptually blanked
(DPMS off), wasting battery power. Could it also turn on the backlight too
early during boot before the panel driver has cleared the screen, causing
visual garbage?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260916-shikra-dt-changes-v4-0-d5d5c3ffe070@oss.qualcomm.com?part=3

  reply	other threads:[~2026-09-16  9:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16  9:11 [PATCH v4 0/4] arm64: qcom: dts: Add display support for Qualcomm Shikra Nabige Aala
2026-09-16  9:11 ` [PATCH v4 1/4] arm64: dts: qcom: shikra: Add MDSS display subsystem Nabige Aala
2026-09-22 16:05   ` Dmitry Baryshkov
2026-09-16  9:11 ` [PATCH v4 2/4] arm64: dts: qcom: shikra-cqs-evk: Enable display and add ili7807s panel Nabige Aala
2026-09-16  9:23   ` sashiko-bot
2026-09-22 16:04   ` Dmitry Baryshkov
2026-09-16  9:11 ` [PATCH v4 3/4] arm64: dts: qcom: shikra-cqm-evk: " Nabige Aala
2026-09-16  9:19   ` sashiko-bot [this message]
2026-09-22 16:03   ` Dmitry Baryshkov
2026-09-23 10:46     ` Arpit Saini
2026-09-23 12:08       ` Dmitry Baryshkov
2026-09-24 18:36         ` Arpit Saini
2026-09-16  9:11 ` [PATCH v4 4/4] arm64: defconfig: Enable ILI7807S DSI panel driver Nabige Aala
2026-09-22 16:03   ` Dmitry Baryshkov

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=20260916091913.8F51F1F0089A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=nabige.aala@oss.qualcomm.com \
    --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