Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Abel Vesa" <abel.vesa@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 08/16] clk: qcom: gcc-qcs615: Tie the CX power domain to controller
Date: Thu, 20 Aug 2026 10:27:34 +0000	[thread overview]
Message-ID: <20260820102734.8B5C11F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260820-qcom-tie-cx-to-gcc-v2-8-e67ea30d8b7b@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Unclocked register access during reset assertion because qcom_reset_ops do not wake the device from RPM suspend.
--

--- Patch [8]: [PATCH v2 08/16] clk: qcom: gcc-qcs615: Tie the CX power domain to controller ---
commit c06f319be5cd4791e28ad1c311d665bbd4af3230
Author: Abel Vesa <abel.vesa@oss.qualcomm.com>

clk: qcom: gcc-qcs615: Tie the CX power domain to controller
    
Enable runtime PM for the controller, allowing CX to be powered down
once all GCC consumers have released their clocks and GDSCs.

> diff --git a/drivers/clk/qcom/gcc-qcs615.c b/drivers/clk/qcom/gcc-qcs615.c
> index 57f8c80c6f324..601c81c844505 100644
> --- a/drivers/clk/qcom/gcc-qcs615.c
> +++ b/drivers/clk/qcom/gcc-qcs615.c
> @@ -2967,6 +2967,7 @@ static const struct qcom_cc_desc gcc_qcs615_desc = {
>  	.resets = gcc_qcs615_resets,
>  	.num_resets = ARRAY_SIZE(gcc_qcs615_resets),
>  	.gdscs = gcc_qcs615_gdscs,
> +	.use_rpm = true,

[Severity: High]
Will enabling runtime PM here cause unclocked register accesses during reset 
assertions?

When use_rpm is set to true, the GCC controller can be runtime suspended. If a 
consumer device driver calls reset_control_assert() before enabling its clocks, 
the underlying reset callback executes a register write without first waking up 
the GCC device.

Looking at the qcom reset operations:

drivers/clk/qcom/reset.c:qcom_reset_set_assert() {
    ...
    regmap_update_bits(rst->regmap, map->reg, mask, assert ? mask : 0);

    /* Read back the register to ensure write completion, ignore the value */
    regmap_read(rst->regmap, map->reg, &mask);
    ...
}

Since there is no pm_runtime_resume_and_get() or similar mechanism to wake the 
controller before the regmap_update_bits() call, will this write to a powered-off 
MMIO space and trigger a synchronous external abort?

>  	.num_gdscs = ARRAY_SIZE(gcc_qcs615_gdscs),
>  };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260820-qcom-tie-cx-to-gcc-v2-0-e67ea30d8b7b@oss.qualcomm.com?part=8

  reply	other threads:[~2026-08-20 10:27 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 10:07 [PATCH v2 00/16] clk: qcom: Tie CX power domains to GCCs Abel Vesa
2026-08-20 10:07 ` [PATCH v2 01/16] clk: qcom: gcc-sm8250: Tie the CX power domain to controller Abel Vesa
2026-08-20 10:25   ` sashiko-bot
2026-08-20 10:29   ` Konrad Dybcio
2026-08-20 10:07 ` [PATCH v2 02/16] clk: qcom: gcc-sm8350: " Abel Vesa
2026-08-20 10:29   ` Konrad Dybcio
2026-08-20 10:07 ` [PATCH v2 03/16] clk: qcom: gcc-sm8450: " Abel Vesa
2026-08-20 10:29   ` Konrad Dybcio
2026-08-20 10:07 ` [PATCH v2 04/16] clk: qcom: gcc-sm8550: " Abel Vesa
2026-08-20 10:29   ` Konrad Dybcio
2026-08-20 10:07 ` [PATCH v2 05/16] clk: qcom: gcc-sm8650: " Abel Vesa
2026-08-20 10:30   ` Konrad Dybcio
2026-08-20 10:07 ` [PATCH v2 06/16] clk: qcom: gcc-sm8750: " Abel Vesa
2026-08-20 10:25   ` sashiko-bot
2026-08-20 10:30   ` Konrad Dybcio
2026-08-20 10:07 ` [PATCH v2 07/16] clk: qcom: gcc-kaanapali: " Abel Vesa
2026-08-20 10:30   ` Konrad Dybcio
2026-08-20 10:07 ` [PATCH v2 08/16] clk: qcom: gcc-qcs615: " Abel Vesa
2026-08-20 10:27   ` sashiko-bot [this message]
2026-08-20 10:30   ` Konrad Dybcio
2026-08-20 10:07 ` [PATCH v2 09/16] arm64: dts: qcom: sm8250: Add GCC CX power domain Abel Vesa
2026-08-20 10:20   ` sashiko-bot
2026-08-20 10:07 ` [PATCH v2 10/16] arm64: dts: qcom: sm8350: " Abel Vesa
2026-08-20 10:19   ` sashiko-bot
2026-08-20 10:07 ` [PATCH v2 11/16] arm64: dts: qcom: sm8450: " Abel Vesa
2026-08-20 10:07 ` [PATCH v2 12/16] arm64: dts: qcom: sm8550: " Abel Vesa
2026-08-20 10:07 ` [PATCH v2 13/16] arm64: dts: qcom: sm8650: " Abel Vesa
2026-08-20 10:21   ` sashiko-bot
2026-08-20 10:07 ` [PATCH v2 14/16] arm64: dts: qcom: sm8750: " Abel Vesa
2026-08-20 10:07 ` [PATCH v2 15/16] arm64: dts: qcom: kaanapali: " Abel Vesa
2026-08-20 10:07 ` [PATCH v2 16/16] arm64: dts: qcom: talos: " Abel Vesa
2026-08-20 10:22   ` sashiko-bot
2026-08-20 10:44 ` [PATCH v2 00/16] clk: qcom: Tie CX power domains to GCCs Abel Vesa

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=20260820102734.8B5C11F000E9@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