From: sashiko-bot@kernel.org
To: "Taniya Das" <taniya.das@oss.qualcomm.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 6/6] clk: qcom: gpucc: Add Nord graphics clock controller support
Date: Tue, 21 Jul 2026 07:18:48 +0000 [thread overview]
Message-ID: <20260721071848.A16D71F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260721-nords_mm_v1-v2-6-17e5a445a512@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `gpu_2_cc_hub_clk_src` clock incorrectly reuses the frequency table for `gpu_2_cc_ff_clk_src`.
--
--- Patch [6]: [PATCH v2 6/6] clk: qcom: gpucc: Add Nord graphics clock controller support ---
commit 09ee5a90eabdc23a86ad541e2815981623d9e1fe
Author: Taniya Das <taniya.das@oss.qualcomm.com>
clk: qcom: gpucc: Add Nord graphics clock controller support
This commit adds support for the GPU and GPU2 clock controllers on the
Qualcomm Nord platform. These controllers provide the clocks required for
the graphics subsystem.
> diff --git a/drivers/clk/qcom/gpu2cc-nord.c b/drivers/clk/qcom/gpu2cc-nord.c
> new file mode 100644
> index 0000000000000..a05ff9fa1506e
> --- /dev/null
> +++ b/drivers/clk/qcom/gpu2cc-nord.c
[ ... ]
> +static struct clk_rcg2 gpu_2_cc_hub_clk_src = {
> + .cmd_rcgr = 0x91a8,
> + .mnd_width = 0,
> + .hid_width = 5,
> + .parent_map = gpu_2_cc_parent_map_2,
> + .freq_tbl = ftbl_gpu_2_cc_ff_clk_src,
[Severity: Medium]
Is this frequency table correct? It looks like gpu_2_cc_hub_clk_src is
reusing the ftbl_gpu_2_cc_ff_clk_src table (200 MHz), rather than having
its own dedicated frequency table.
In gpucc-nord.c, the equivalent hub clock has its own table configured for
300 MHz. Will this reuse cause the GPU2 hub to be underclocked when the
GPU2 subsystem requests its hub clock rate?
> + .hw_clk_ctrl = true,
> + .clkr.hw.init = &(const struct clk_init_data) {
> + .name = "gpu_2_cc_hub_clk_src",
> + .parent_data = gpu_2_cc_parent_data_2,
> + .num_parents = ARRAY_SIZE(gpu_2_cc_parent_data_2),
> + .flags = CLK_SET_RATE_PARENT,
> + .ops = &clk_rcg2_shared_ops,
> + },
> +};
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260721-nords_mm_v1-v2-0-17e5a445a512@oss.qualcomm.com?part=6
prev parent reply other threads:[~2026-07-21 7:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 7:07 [PATCH v2 0/6] clk: qcom: Add Nord multimedia clock controller support Taniya Das
2026-07-21 7:07 ` [PATCH v2 1/6] clk: qcom: gcc-nord: mark PCIe link clocks as critical Taniya Das
2026-07-21 7:07 ` [PATCH v2 2/6] clk: qcom: negcc-nord: keep GPU2 CFG clock enabled via critical CBCR Taniya Das
2026-07-21 7:07 ` [PATCH v2 3/6] dt-bindings: clock: qcom: Document Nord display clock controller Taniya Das
2026-07-21 7:07 ` [PATCH v2 4/6] clk: qcom: Add Nord display clock controller support Taniya Das
2026-07-21 7:07 ` [PATCH v2 5/6] dt-bindings: clock: qcom: Document Nord GPU clock controllers Taniya Das
2026-07-21 7:14 ` sashiko-bot
2026-07-21 7:07 ` [PATCH v2 6/6] clk: qcom: gpucc: Add Nord graphics clock controller support Taniya Das
2026-07-21 7:18 ` sashiko-bot [this message]
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=20260721071848.A16D71F000E9@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