From: sashiko-bot@kernel.org
To: "Qiang Yu" <qiang.yu@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] clk: qcom: tcsrcc-x1e80100: Migrate to clk_ref helper
Date: Wed, 15 Jul 2026 02:49:31 +0000 [thread overview]
Message-ID: <20260715024932.31A621F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260714-hamoa_tcsr_qref_0714_2-v1-2-13047922a376@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch relies on an undeclared structure, an undeclared function, and a non-existent header file, which will cause a fatal build error.
--
--- Patch [2]: [PATCH 2/3] clk: qcom: tcsrcc-x1e80100: Migrate to clk_ref helper ---
commit c9be5146280c763b773fd80f0650fab3bbb0c928
Author: Qiang Yu <qiang.yu@oss.qualcomm.com>
clk: qcom: tcsrcc-x1e80100: Migrate to clk_ref helper
Replaces local clk_branch-based clkref definitions with descriptor-based
registration via qcom_clk_ref_probe(). This simplifies the driver to
focus on metadata and reuses common runtime logic.
> diff --git a/drivers/clk/qcom/tcsrcc-x1e80100.c b/drivers/clk/qcom/tcsrcc-x1e80100.c
> index 0b05c27b619b6..ad1f6be83a53e 100644
> --- a/drivers/clk/qcom/tcsrcc-x1e80100.c
> +++ b/drivers/clk/qcom/tcsrcc-x1e80100.c
> @@ -5,252 +5,141 @@
> */
>
> #include <linux/clk-provider.h>
> +#include <linux/clk/qcom.h>
[Severity: Low]
Does this header exist in the kernel tree? It appears that <linux/clk/qcom.h>
is missing, which will cause a fatal build error.
> #include <linux/module.h>
> +#include <linux/of.h>
[ ... ]
> +static const struct regmap_config tcsr_cc_x1e80100_regmap_config = {
> + .reg_bits = 32,
> + .reg_stride = 4,
> + .val_bits = 32,
> + .max_register = 0x2f000,
> + .fast_io = true,
> +};
>
> +static const struct qcom_clk_ref_desc * const tcsr_cc_x1e80100_clk_descs[] = {
[Severity: Low]
Since the header is missing, is struct qcom_clk_ref_desc defined anywhere?
This seems to also cause a build error.
> + [TCSR_EDP_CLKREF_EN] = &(const struct qcom_clk_ref_desc) {
> + .name = "tcsr_edp_clkref_en",
[ ... ]
> static int tcsr_cc_x1e80100_probe(struct platform_device *pdev)
> {
> - return qcom_cc_probe(pdev, &tcsr_cc_x1e80100_desc);
> + return qcom_clk_ref_probe(pdev, &tcsr_cc_x1e80100_regmap_config,
> + tcsr_cc_x1e80100_clk_descs,
> + ARRAY_SIZE(tcsr_cc_x1e80100_clk_descs));
[Severity: Low]
Is qcom_clk_ref_probe() declared elsewhere? It seems to be missing along with
the header and the struct definition. Should there be a prerequisite patch
introducing these helpers?
> }
>
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260714-hamoa_tcsr_qref_0714_2-v1-0-13047922a376@oss.qualcomm.com?part=2
next prev parent reply other threads:[~2026-07-15 2:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 2:40 [PATCH 0/3] clk: qcom: Migrate x1e80100 TCSR to clk_ref helper Qiang Yu
2026-07-15 2:40 ` [PATCH 1/3] dt-bindings: clock: qcom: Move x1e80100 TCSR to own binding Qiang Yu
2026-07-15 2:47 ` sashiko-bot
2026-07-15 2:40 ` [PATCH 2/3] clk: qcom: tcsrcc-x1e80100: Migrate to clk_ref helper Qiang Yu
2026-07-15 2:49 ` sashiko-bot [this message]
2026-07-15 2:40 ` [PATCH 3/3] arm64: dts: qcom: hamoa/purwa: Add QREF regulator supplies Qiang Yu
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=20260715024932.31A621F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=qiang.yu@oss.qualcomm.com \
--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