Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Abel Vesa" <abel.vesa@oss.qualcomm.com>
Cc: conor+dt@kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v5 35/42] arm64: dts: qcom: sm8150: Add GCC CX power domain
Date: Thu, 24 Sep 2026 11:01:21 +0000	[thread overview]
Message-ID: <20260924110121.C66B21F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260924-qcom-tie-cx-to-gcc-v5-35-38732033e5b5@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] clk: qcom: sm8150: missing runtime PM support pins CX power domain ON
--

commit acb1efde8c25f0a90d262048322b01fb3721956e
Author: Abel Vesa <abel.vesa@oss.qualcomm.com>

arm64: dts: qcom: sm8150: Add GCC CX power domain

This commit adds the CX power domain reference to the GCC node in the sm8150
device tree. This allows GCC GDSC consumers to propagate their votes to the
RPMh CX domain.

> diff --git a/arch/arm64/boot/dts/qcom/sm8150.dtsi b/arch/arm64/boot/dts/qcom/sm8150.dtsi
> index 94a3b02cb2897..397c0142ea579 100644
> --- a/arch/arm64/boot/dts/qcom/sm8150.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8150.dtsi
> @@ -913,6 +913,7 @@ gcc: clock-controller@100000 {
>  				      "sleep_clk";
>  			clocks = <&rpmhcc RPMH_CXO_CLK>,
>  				 <&sleep_clk>;
> +			power-domains = <&rpmhpd SM8150_CX>;

[Severity: High]
Does adding this property pin the CX power domain ON indefinitely?

Looking at the gcc-sm8150.c driver, it seems .use_rpm is not set to true in
gcc_sm8150_desc. Because of this, qcom_cc_really_probe() skips calling
devm_pm_runtime_enable() for this device.

When platform_probe() attaches the GCC device to the CX domain, it uses
PD_FLAG_ATTACH_POWER_ON, which powers the domain ON. However, since runtime
PM is never enabled on the GCC device, its disable_depth remains 1, causing
pm_runtime_suspended() to always return false.

Since the genpd core evaluates if all attached devices are suspended before
powering off the domain, it seems genpd_power_off() will never power off the
CX domain here. This regression could prevent the SoC from entering deep
sleep states (power collapse) and cause battery drain.

Does gcc-sm8150.c need .use_rpm = true added to gcc_sm8150_desc so the
device can suspend and the domain can be powered off? 

(Note: this same behavior appears to affect sm8250 as its driver also lacks
.use_rpm = true).

>  		};
>  
>  		gpi_dma0: dma-controller@800000 {

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260924-qcom-tie-cx-to-gcc-v5-0-38732033e5b5@oss.qualcomm.com?part=35

  reply	other threads:[~2026-09-24 11:01 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 10:39 [PATCH v5 00/42] clk: qcom: Tie CX power domains to GCCs Abel Vesa
2026-09-24 10:39 ` [PATCH v5 01/42] dt-bindings: clock: qcom: gcc-sdm845: Require CX power domain Abel Vesa
2026-09-24 10:39 ` [PATCH v5 02/42] dt-bindings: clock: qcom: gcc-sm8150: Add " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 03/42] dt-bindings: clock: qcom: gcc-sm8250: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 04/42] dt-bindings: clock: qcom: gcc-sm8350: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 05/42] dt-bindings: clock: qcom: gcc-sm8450: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 06/42] dt-bindings: clock: qcom: qcs615-gcc: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 07/42] dt-bindings: clock: qcom: sm8550-gcc: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 08/42] dt-bindings: clock: qcom: sm8650-gcc: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 09/42] dt-bindings: clock: qcom: sm8750-gcc: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 10/42] dt-bindings: clock: qcom: sm4450-gcc: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 11/42] dt-bindings: clock: qcom: gcc-sm6350: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 12/42] dt-bindings: clock: qcom: qcs8300-gcc: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 13/42] dt-bindings: clock: qcom: sdx75-gcc: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 14/42] clk: qcom: gcc-eliza: Tie the CX power domain to controller Abel Vesa
2026-09-24 10:39 ` [PATCH v5 15/42] clk: qcom: gcc-kaanapali: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 16/42] clk: qcom: gcc-qcs8300: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 17/42] clk: qcom: gcc-sa8775p: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 18/42] clk: qcom: gcc-sar2130p: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 19/42] clk: qcom: gcc-sc7280: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 20/42] clk: qcom: gcc-sdx75: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 21/42] clk: qcom: gcc-sm4450: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 22/42] clk: qcom: gcc-sm8350: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 23/42] clk: qcom: gcc-sm8450: " Abel Vesa
2026-09-24 11:11   ` sashiko-bot
2026-09-25 15:47     ` Abel Vesa
2026-09-24 10:39 ` [PATCH v5 24/42] clk: qcom: gcc-sm8550: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 25/42] clk: qcom: gcc-sm8650: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 26/42] clk: qcom: gcc-sm8750: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 27/42] clk: qcom: gcc-x1e80100: " Abel Vesa
2026-09-24 11:08   ` sashiko-bot
2026-09-25 15:48     ` Abel Vesa
2026-09-24 10:39 ` [PATCH v5 28/42] arm64: dts: qcom: kaanapali: Add GCC CX power domain Abel Vesa
2026-09-24 10:39 ` [PATCH v5 29/42] arm64: dts: qcom: monaco: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 30/42] arm64: dts: qcom: sar2130p: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 31/42] arm64: dts: qcom: sdm670: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 32/42] arm64: dts: qcom: sdx75: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 33/42] arm64: dts: qcom: sm4450: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 34/42] arm64: dts: qcom: sm6350: " Abel Vesa
2026-09-24 11:02   ` sashiko-bot
2026-09-25 15:53     ` Abel Vesa
2026-09-24 10:39 ` [PATCH v5 35/42] arm64: dts: qcom: sm8150: " Abel Vesa
2026-09-24 11:01   ` sashiko-bot [this message]
2026-09-25 16:01     ` Abel Vesa
2026-09-24 10:39 ` [PATCH v5 36/42] arm64: dts: qcom: sm8250: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 37/42] arm64: dts: qcom: sm8350: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 38/42] arm64: dts: qcom: sm8450: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 39/42] arm64: dts: qcom: sm8550: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 40/42] arm64: dts: qcom: sm8650: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 41/42] arm64: dts: qcom: sm8750: " Abel Vesa
2026-09-24 10:39 ` [PATCH v5 42/42] arm64: dts: qcom: talos: " Abel Vesa
2026-09-25 16:43 ` (subset) [PATCH v5 00/42] clk: qcom: Tie CX power domains to GCCs Bjorn Andersson
2026-09-29 21:50   ` Rob Herring
2026-10-01  0:40     ` Bjorn Andersson
2026-10-01 14:39 ` Bjorn Andersson

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=20260924110121.C66B21F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=abel.vesa@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.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