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 2/4] arm64: dts: qcom: shikra-cqs-evk: Enable display and add ili7807s panel
Date: Wed, 16 Sep 2026 09:23:45 +0000	[thread overview]
Message-ID: <20260916092345.EAF721F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260916-shikra-dt-changes-v4-2-d5d5c3ffe070@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dts: qcom: backlight left on during screen blanking due to static pinctrl
--

commit 720635a18d3694cb65f6d9de1eaf9550b30b64e1
Author: Arpit Saini <arpit.saini@oss.qualcomm.com>

arm64: dts: qcom: shikra-cqs-evk: Enable display and add ili7807s panel
    
Enable the Shikra MDSS display subsystem on the Qualcomm Shikra CQS EVK
board and add the DLC0697 MIPI DSI display panel node.

> diff --git a/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts b/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts
> index e62ba5aef71ff..a9067b710a224 100644
> --- a/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts
> +++ b/arch/arm64/boot/dts/qcom/shikra-cqs-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>;
> +		pinctrl-1 = <&panel_rst_n_suspend &panel_bl_en_suspend>;
> +		pinctrl-names = "default", "sleep";

[Severity: Medium]
Will this configuration leave the backlight on when the screen is blanked?

Since the default pinctrl state is applied unconditionally during device
probe, the backlight enable pin is statically driven high by the
panel_bl_en node.

The DRM framework does not transition a device's pinctrl to the sleep
state when a display is blanked at runtime, such as during a screen timeout.
It typically only engages sleep states during a full system suspend.

This means when the screen is logically blanked, the backlight will remain
actively driven high, even though the panel's data pipeline may be cut.

Could the backlight enable be modeled as a dynamic gpio-backlight device
node and linked to the panel via a backlight property, or handled via a
dedicated GPIO property in the panel driver, instead of bypassing DRM
runtime power management with static pinctrl?

[ ... ]

> +&tlmm {

[ ... ]

> +	panel_bl_en: panel-bl-en-state {
> +		pins = "gpio91";
> +		function = "gpio";
> +		drive-strength = <2>;
> +		bias-disable;
> +		output-high;
> +	};
> +
> +	panel_bl_en_suspend: panel-bl-en-suspend-state {
> +		pins = "gpio91";
> +		function = "gpio";
> +		drive-strength = <2>;
> +		bias-pull-down;
> +		output-low;
> +	};

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

  reply	other threads:[~2026-09-16  9:23 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 [this message]
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
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=20260916092345.EAF721F000FF@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