From: sashiko-bot@kernel.org
To: "Hardeep Sharma" <hardeep.sharma@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org,
linux-clk@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 11/15] clk: qcom: Add Global Clock Controller driver for Kuno
Date: Fri, 21 Aug 2026 16:25:58 +0000 [thread overview]
Message-ID: <20260821162558.8067C1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260821-kuno-soc-support-v3-11-196e2b306368@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Local branch clocks like `gcc_usb20_master_clk` incorrectly use `BRANCH_HALT_VOTED` instead of `BRANCH_HALT`.
--
--- Patch [11]: [PATCH v3 11/15] clk: qcom: Add Global Clock Controller driver for Kuno ---
commit 87ef960371a78ac9a0bb9691a723f3b871043695
Author: Hardeep Sharma <hardeep.sharma@oss.qualcomm.com>
Subject: clk: qcom: Add Global Clock Controller driver for Kuno
Add the global clock controller (GCC) driver for the Qualcomm Kuno SoC,
providing the PLLs, root clock generators, gate/branch clocks and resets
used by the peripheral devices.
> diff --git a/drivers/clk/qcom/gcc-kuno.c b/drivers/clk/qcom/gcc-kuno.c
> new file mode 100644
> index 0000000000000..f7401ae315dd0
> --- /dev/null
> +++ b/drivers/clk/qcom/gcc-kuno.c
[ ... ]
> +static struct clk_branch gcc_emac0_axi_clk = {
> + .halt_reg = 0x71018,
> + .halt_check = BRANCH_HALT_VOTED,
> + .hwcg_reg = 0x71018,
> + .hwcg_bit = 1,
> + .clkr = {
> + .enable_reg = 0x71018,
> + .enable_mask = BIT(0),
[Severity: High]
Does this EMAC clock use the correct halt check? Since enable_reg and halt_reg
are the same (0x71018), this appears to be a local branch clock rather than an
APCS voted clock.
Using BRANCH_HALT_VOTED bypasses the halt check entirely, which could allow
the kernel to return from clk_enable() before the clock has physically started,
potentially causing unclocked hardware accesses. Should this use BRANCH_HALT
instead?
[ ... ]
> +static struct clk_branch gcc_usb20_master_clk = {
> + .halt_reg = 0x27018,
> + .halt_check = BRANCH_HALT_VOTED,
> + .clkr = {
> + .enable_reg = 0x27018,
> + .enable_mask = BIT(0),
[Severity: High]
Similarly, does gcc_usb20_master_clk incorrectly use BRANCH_HALT_VOTED?
Its enable_reg is the same as halt_reg (0x27018), so bypassing the halt check
might lead to unclocked hardware accesses during device probe or power
management transitions.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260821-kuno-soc-support-v3-0-196e2b306368@oss.qualcomm.com?part=11
next prev parent reply other threads:[~2026-08-21 16:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 16:08 [PATCH v3 00/15] Add initial support for Qualcomm Kuno SoC Hardeep Sharma
2026-08-21 16:08 ` [PATCH v3 01/15] soc: qcom: geni-se: allow selection on 32-bit ARM Qualcomm SoCs Hardeep Sharma
2026-08-24 7:59 ` Abel Vesa
2026-08-21 16:08 ` [PATCH v3 02/15] dt-bindings: power: rpmpd: Document Kuno RPMh power domains Hardeep Sharma
2026-08-21 16:08 ` [PATCH v3 03/15] pmdomain: qcom: rpmhpd: Add power domains for Kuno Hardeep Sharma
2026-08-24 7:58 ` Abel Vesa
2026-08-21 16:08 ` [PATCH v3 04/15] dt-bindings: clock: qcom,rpmhcc: Add Kuno RPMh clock controller Hardeep Sharma
2026-08-21 16:08 ` [PATCH v3 05/15] clk: qcom: clk-rpmh: Add support for Kuno RPMh clocks Hardeep Sharma
2026-08-21 16:21 ` sashiko-bot
2026-08-24 7:46 ` Abel Vesa
2026-08-21 16:08 ` [PATCH v3 06/15] dt-bindings: interconnect: Add Qualcomm Kuno NoC Hardeep Sharma
2026-08-21 16:09 ` [PATCH v3 07/15] interconnect: qcom: Add Kuno interconnect provider driver Hardeep Sharma
2026-08-24 7:57 ` Abel Vesa
2026-08-21 16:09 ` [PATCH v3 08/15] dt-bindings: pinctrl: qcom: Add Kuno TLMM Hardeep Sharma
2026-08-21 16:09 ` [PATCH v3 09/15] pinctrl: qcom: Add Kuno pinctrl driver Hardeep Sharma
2026-08-24 7:50 ` Abel Vesa
2026-08-21 16:09 ` [PATCH v3 10/15] dt-bindings: clock: qcom: Add Kuno Global Clock Controller Hardeep Sharma
2026-08-21 16:18 ` sashiko-bot
2026-08-21 16:09 ` [PATCH v3 11/15] clk: qcom: Add Global Clock Controller driver for Kuno Hardeep Sharma
2026-08-21 16:25 ` sashiko-bot [this message]
2026-08-24 7:40 ` Abel Vesa
2026-08-21 16:09 ` [PATCH v3 12/15] dt-bindings: interrupt-controller: qcom,pdc: Add Kuno compatible string Hardeep Sharma
2026-08-21 16:09 ` [PATCH v3 13/15] dt-bindings: firmware: qcom,scm: Document SCM on Kuno SoC Hardeep Sharma
2026-08-21 16:09 ` [PATCH v3 14/15] dt-bindings: arm: qcom: Document Kuno IDP board Hardeep Sharma
2026-08-21 16:09 ` [PATCH v3 15/15] ARM: dts: qcom: Add initial device tree for Kuno SoC Hardeep Sharma
2026-08-21 16:23 ` sashiko-bot
2026-08-24 7:45 ` 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=20260821162558.8067C1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hardeep.sharma@oss.qualcomm.com \
--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