From: sashiko-bot@kernel.org
To: "Stephan Gerhold" <stephan.gerhold@linaro.org>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 07/12] clk: qcom: gcc-mdm9607: Drop incorrect apss_tcu_clk_src
Date: Tue, 09 Jun 2026 14:27:10 +0000 [thread overview]
Message-ID: <20260609142710.98DDF1F0089A@smtp.kernel.org> (raw)
In-Reply-To: <20260609-qcom-clk-mdm9607-fixes-v1-7-5e9717faf842@linaro.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Removing `apss_tcu_clk_src` leaves the static constant arrays `gcc_xo_gpll0_gpll1_gpll2` and `gcc_xo_gpll0_gpll1_gpll2_map` completely unused.
--
commit 358707fc8fbfb6b33cbd35ecd5569222e1050407
Author: Stephan Gerhold <stephan@gerhold.net>
clk: qcom: gcc-mdm9607: Drop incorrect apss_tcu_clk_src
This commit removes the apss_tcu_clk_src clock from the MDM9607 GCC driver
as it does not seem to exist on this hardware. Reading or writing its
registers results in 0 or crashes, and its frequency table math was
broken.
> diff --git a/drivers/clk/qcom/gcc-mdm9607.c b/drivers/clk/qcom/gcc-mdm9607.c
> --- a/drivers/clk/qcom/gcc-mdm9607.c
> +++ b/drivers/clk/qcom/gcc-mdm9607.c
[ ... ]
> @@ -677,26 +677,6 @@ static struct clk_rcg2 sdcc2_apps_clk_src = {
> },
> };
>
> -static const struct freq_tbl ftbl_gcc_apss_tcu_clk[] = {
> - F(155000000, P_GPLL2, 6, 0, 0),
> - F(310000000, P_GPLL2, 3, 0, 0),
> - F(400000000, P_GPLL0, 2, 0, 0),
> - { }
> -};
> -
> -static struct clk_rcg2 apss_tcu_clk_src = {
> - .cmd_rcgr = 0x1207c,
> - .hid_width = 5,
> - .parent_map = gcc_xo_gpll0_gpll1_gpll2_map,
[Severity: Low]
Does the removal of apss_tcu_clk_src leave gcc_xo_gpll0_gpll1_gpll2_map
unused?
It looks like this clock was the sole user of this static array. Leaving it
unreferenced might cause -Wunused-const-variable compiler warnings.
> - .freq_tbl = ftbl_gcc_apss_tcu_clk,
> - .clkr.hw.init = &(struct clk_init_data){
> - .name = "apss_tcu_clk_src",
> - .parent_data = gcc_xo_gpll0_gpll1_gpll2,
[Severity: Low]
Similarly, does this also leave the gcc_xo_gpll0_gpll1_gpll2 static array
unused?
If there are no other references in drivers/clk/qcom/gcc-mdm9607.c, it
should likely be removed as well to prevent dead code and warnings.
> - .num_parents = 4,
> - .ops = &clk_rcg2_ops,
> - },
> -};
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260609-qcom-clk-mdm9607-fixes-v1-0-5e9717faf842@linaro.org?part=7
next prev parent reply other threads:[~2026-06-09 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 14:14 [PATCH 00/12] clk: qcom: Assorted fixes for gcc-mdm9607 (and gcc-msm8916/39) Stephan Gerhold
2026-06-09 14:14 ` [PATCH 01/12] clk: qcom: gcc-msm8916: Fix enable_reg for gcc_blsp1_sleep_clk Stephan Gerhold
2026-06-09 14:14 ` [PATCH 02/12] clk: qcom: gcc-msm8939: " Stephan Gerhold
2026-06-09 14:14 ` [PATCH 03/12] clk: qcom: gcc-mdm9607: " Stephan Gerhold
2026-06-09 14:14 ` [PATCH 04/12] clk: qcom: gcc-mdm9607: Fix BIMC PLL definition Stephan Gerhold
2026-06-09 14:14 ` [PATCH 05/12] clk: qcom: gcc-mdm9607: Fix halt_reg for gcc_apss_axi_clk Stephan Gerhold
2026-06-09 14:14 ` [PATCH 06/12] clk: qcom: gcc-mdm9607: Increase delay for USB PHY reset Stephan Gerhold
2026-06-09 14:14 ` [PATCH 07/12] clk: qcom: gcc-mdm9607: Drop incorrect apss_tcu_clk_src Stephan Gerhold
2026-06-09 14:27 ` sashiko-bot [this message]
2026-06-09 14:14 ` [PATCH 08/12] clk: qcom: gcc-mdm9607: Drop incorrect system_noc_bfdcd_clk_src Stephan Gerhold
2026-06-09 14:14 ` [PATCH 09/12] dt-bindings: clock: qcom: gcc-mdm9607: Drop incorrect clocks Stephan Gerhold
2026-06-09 14:14 ` [PATCH 10/12] dt-bindings: clock: qcom,gcc-mdm9607: Add missing "clocks" property Stephan Gerhold
2026-06-09 14:14 ` [PATCH 11/12] dt-bindings: clock: qcom,gcc-mdm9607: Use proper address in example Stephan Gerhold
2026-06-09 14:14 ` [PATCH 12/12] clk: qcom: gcc-mdm9607: Drop redundant register update during probe Stephan Gerhold
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=20260609142710.98DDF1F0089A@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=stephan.gerhold@linaro.org \
/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