From: sashiko-bot@kernel.org
To: "Taniya Das" <taniya.das@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 3/5] dt-bindings: clock: qcom: Add Maili global clock controller
Date: Thu, 18 Jun 2026 17:28:59 +0000 [thread overview]
Message-ID: <20260618172900.0954D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260618-maili_initial_clock-v1-3-d6ede0352113@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The dt-bindings header is missing the Block Control Reset (BCR) macro for the newly added QUPV3_WRAP5.
--
commit 9b94fa834ca764c84f27ddbfa19843cbf9fd8f24
Author: Taniya Das <taniya.das@oss.qualcomm.com>
dt-bindings: clock: qcom: Add Maili global clock controller
This commit adds device tree bindings for the global clock controller on the
Qualcomm Maili SoC. It extends the existing Hawi GCC bindings by adding a
few additional clocks specific to Maili.
> diff --git a/include/dt-bindings/clock/qcom,hawi-gcc.h b/include/dt-bindings/clock/qcom,hawi-gcc.h
> index 6cd7fa0884f53..9e0e382af3112 100644
> --- a/include/dt-bindings/clock/qcom,hawi-gcc.h
> +++ b/include/dt-bindings/clock/qcom,hawi-gcc.h
[ ... ]
> @@ -196,6 +196,16 @@
> #define GCC_VIDEO_AXI0C_CLK 186
> #define GCC_VIDEO_XO_CLK 187
>
> +/* Maili has below additional clocks on top of Hawi */
> +#define GCC_QUPV3_WRAP5_CORE_2X_CLK 188
> +#define GCC_QUPV3_WRAP5_CORE_CLK 189
> +#define GCC_QUPV3_WRAP5_QSPI_REF_CLK 190
> +#define GCC_QUPV3_WRAP5_QSPI_REF_CLK_SRC 191
> +#define GCC_QUPV3_WRAP5_S0_CLK 192
> +#define GCC_QUPV3_WRAP5_S0_CLK_SRC 193
> +#define GCC_QUPV3_WRAP_5_M_AHB_CLK 194
> +#define GCC_QUPV3_WRAP_5_S_AHB_CLK 195
[Severity: Medium]
Does this hardware block also require a Block Control Reset macro?
Qualcomm GCC architectures typically provide a corresponding BCR macro for
every QUPv3 wrapper block (like GCC_QUPV3_WRAPPER_1_BCR) so the serial
engine drivers can reset the hardware.
Since this patch adds the clocks for QUPV3_WRAP5, should there also be a
GCC_QUPV3_WRAPPER_5_BCR added to the reset section of this header? Without
this definition, the device tree might not be able to specify the reset for
wrapper 5, which could prevent dependent drivers from properly recovering
the hardware.
> +
> /* GCC power domains */
> #define GCC_PCIE_0_GDSC 0
> #define GCC_PCIE_0_PHY_GDSC 1
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260618-maili_initial_clock-v1-0-d6ede0352113@oss.qualcomm.com?part=3
next prev parent reply other threads:[~2026-06-18 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 17:21 [PATCH 0/5] clk: qcom: Introduce initial clock controllers for Maili SoC Taniya Das
2026-06-18 17:21 ` [PATCH 1/5] dt-bindings: clock: qcom-rpmhcc: Add RPMH clock controller for Maili Taniya Das
2026-06-18 17:21 ` [PATCH 2/5] dt-bindings: clock: qcom: Add Maili TCSR clock controller Taniya Das
2026-06-18 17:21 ` [PATCH 3/5] dt-bindings: clock: qcom: Add Maili global " Taniya Das
2026-06-18 17:28 ` sashiko-bot [this message]
2026-06-18 17:21 ` [PATCH 4/5] clk: qcom: gcc-hawi: Add support for global clock controller on Maili Taniya Das
2026-06-18 17:21 ` [PATCH 5/5] dt-bindings: mailbox: qcom: Document Maili CPUCP mailbox controller Taniya Das
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=20260618172900.0954D1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=taniya.das@oss.qualcomm.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