From: sashiko-bot@kernel.org
To: "Sreeshankar K" <sreeshankar0910@gmail.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v12 2/6] clk: qcom: Add Global Clock Controller (GCC) driver for SM7250
Date: Wed, 04 Nov 2026 08:14:08 +0000 [thread overview]
Message-ID: <sashiko-outbox-196867@kernel.org> (raw)
In-Reply-To: <20261104-master-v12-2-57fbe9eef978@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] clk: qcom: gcc-sm7250: wrong halt_check on gcc_ddrss_gpu_axi_clk
--
commit a24e620aee1e1a738b8a01486a74fa9dab88eef4
Author: Sreeshankar K <sreeshankar0910@gmail.com>
clk: qcom: Add Global Clock Controller (GCC) driver for SM7250
This commit adds the Global Clock Controller (GCC) driver for Qualcomm SM7250
SoCs, registering PLLs, RCGs, branch clocks, GDSCs, and resets.
> diff --git a/drivers/clk/qcom/gcc-sm7250.c b/drivers/clk/qcom/gcc-sm7250.c
> new file mode 100644
> index 0000000000000..949a12ae93c99
> --- /dev/null
> +++ b/drivers/clk/qcom/gcc-sm7250.c
> @@ -0,0 +1,2278 @@
[ ... ]
> +static struct clk_branch gcc_ddrss_gpu_axi_clk = {
> + .halt_reg = 0x71154,
> + .halt_check = BRANCH_HALT,
> + .clkr = {
> + .enable_reg = 0x71154,
> + .enable_mask = BIT(0),
> + .hw.init = &(const struct clk_init_data){
> + .name = "gcc_ddrss_gpu_axi_clk",
> + .ops = &clk_branch2_ops,
> + },
> + },
> +};
[Severity: Medium]
As reported by Taniya Das on v9 [1], should gcc_ddrss_gpu_axi_clk use
BRANCH_VOTED instead of BRANCH_HALT for .halt_check?
When gcc_ddrss_gpu_axi_clk is disabled via
clk_branch2_disable() -> clk_branch_toggle() -> clk_branch_wait() in
drivers/clk/qcom/clk-branch.c:
bool voted = br->halt_check & BRANCH_VOTED;
...
if (br->halt_check == BRANCH_HALT_DELAY || (!enabling && voted)) {
udelay(10);
} else if (br->halt_check == BRANCH_HALT_ENABLE ||
br->halt_check == BRANCH_HALT ||
(enabling && voted)) {
int count = 200;
while (count-- > 0) {
if (check_halt(br, enabling))
return 0;
udelay(1);
}
WARN(1, "%s status stuck at 'o%s'", name,
enabling ? "ff" : "n");
return -EBUSY;
}
Having .halt_check set to BRANCH_HALT instead of BRANCH_VOTED causes
clk_branch_wait() to poll the CBCR_CLK_OFF bit on disable rather than
delaying 10us, which can trigger a WARN() splat if the voted DDRSS GPU AXI
clock remains active.
[1] https://lore.kernel.org/r/1ea96c7d-102a-4261-a70e-ca0813490a02@oss.qualcomm.com
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261104-master-v12-0-57fbe9eef978@gmail.com?part=2
next prev parent reply other threads:[~2026-11-04 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 7:46 [PATCH v12 0/6] Add initial support for Qualcomm SM7250 SoC Sreeshankar K
2026-11-04 7:46 ` [PATCH v12 1/6] dt-bindings: clock: Add SM7250 global clock controller Sreeshankar K
2026-11-04 7:46 ` [PATCH v12 2/6] clk: qcom: Add Global Clock Controller (GCC) driver for SM7250 Sreeshankar K
2026-11-04 8:14 ` sashiko-bot [this message]
2026-11-04 7:46 ` [PATCH v12 3/6] dt-bindings: firmware: qcom,scm: Document SM7250 SCM Sreeshankar K
2026-11-04 7:46 ` [PATCH v12 4/6] dt-bindings: cpufreq: qcom-hw: Document SM7250 cpufreq hardware Sreeshankar K
2026-11-04 7:46 ` [PATCH v12 5/6] dt-bindings: thermal: lmh: Document SM7250 LMh Sreeshankar K
2026-11-04 7:46 ` [PATCH v12 6/6] arm64: dts: qcom: Add SM7250 devicetree file Sreeshankar K
2026-11-04 8:18 ` sashiko-bot
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=sashiko-outbox-196867@kernel.org \
--to=sashiko-bot@kernel.org \
--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 \
--cc=sreeshankar0910@gmail.com \
/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