From: sashiko-bot@kernel.org
To: "Qiang Yu" <qiang.yu@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v8 5/7] clk: qcom: tcsrcc-glymur: Add Mahua QREF regulator support
Date: Wed, 08 Jul 2026 10:39:10 +0000 [thread overview]
Message-ID: <20260708103911.470351F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260708-tcsr_qref_0708-v8-5-62c42b5fa269@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Missing QREF regulators for TCSR_USB4_1_CLKREF_EN clock in Mahua descriptor table.
--
--- Patch [5]: [PATCH v8 5/7] clk: qcom: tcsrcc-glymur: Add Mahua QREF regulator support ---
commit 1a2cccf8fe12339a5d989a6a9c397fb34f4adf6c
Author: Qiang Yu <qiang.yu@oss.qualcomm.com>
clk: qcom: tcsrcc-glymur: Add Mahua QREF regulator support
Mahua is based on Glymur but uses a different QREF topology, requiring
distinct regulator lists and clock descriptors for its PCIe clock
references. Add mahua-specific regulator arrays and clk descriptor table,
and use match_data to select the correct descriptor table per compatible
string at probe time.
> diff --git a/drivers/clk/qcom/tcsrcc-glymur.c b/drivers/clk/qcom/tcsrcc-glymur.c
> index e0b545258ba4c..1791e23739ed4 100644
> --- a/drivers/clk/qcom/tcsrcc-glymur.c
> +++ b/drivers/clk/qcom/tcsrcc-glymur.c
[ ... ]
> +static const struct qcom_clk_ref_desc * const tcsr_cc_mahua_clk_descs[] = {
[ ... ]
> + [TCSR_USB3_1_CLKREF_EN] = &(const struct qcom_clk_ref_desc) {
> + .name = "tcsr_usb3_1_clkref_en",
> + .offset = 0x68,
> + .regulator_names = mahua_tcsr_tx1_rpt345_rx3_regulators,
> + .num_regulators = ARRAY_SIZE(mahua_tcsr_tx1_rpt345_rx3_regulators),
> + },
> + [TCSR_USB4_1_CLKREF_EN] = &(const struct qcom_clk_ref_desc) {
> + .name = "tcsr_usb4_1_clkref_en",
> + .offset = 0x44,
> + },
[Severity: High]
Are regulators intentionally omitted for TCSR_USB4_1_CLKREF_EN in the Mahua
descriptor table?
If the USB PHY driver requests and enables this clock, the clock framework
will skip regulator voting because .num_regulators is 0. The clock enable
register bit will toggle, but the underlying QREF PHY block will remain
unpowered. On Qualcomm platforms, accessing unpowered PHY blocks typically
causes synchronous external aborts leading to a kernel panic.
In the Glymur configuration, this clock shared the tx0_rx5 regulators with
TCSR_PCIE_1_CLKREF_EN. In Mahua, PCIE_1 was removed but USB4_1 remains
without regulators. Should this include the appropriate regulator names and
num_regulators?
> + [TCSR_USB4_2_CLKREF_EN] = &(const struct qcom_clk_ref_desc) {
> + .name = "tcsr_usb4_2_clkref_en",
> + .offset = 0x5c,
> + .regulator_names = mahua_tcsr_tx1_rpt01_rx1_regulators,
> + .num_regulators = ARRAY_SIZE(mahua_tcsr_tx1_rpt01_rx1_regulators),
> + },
> +};
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260708-tcsr_qref_0708-v8-0-62c42b5fa269@oss.qualcomm.com?part=5
next prev parent reply other threads:[~2026-07-08 10:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 10:02 [PATCH v8 0/7] clk: qcom: Add common clkref support and migrate Glymur and Mahua Qiang Yu
2026-07-08 10:02 ` [PATCH v8 1/7] dt-bindings: clock: qcom: Move glymur TCSR to own binding Qiang Yu
2026-07-08 10:09 ` sashiko-bot
2026-07-09 7:48 ` Krzysztof Kozlowski
2026-07-08 10:02 ` [PATCH v8 2/7] dt-bindings: clock: qcom,glymur-tcsr: Add mahua support Qiang Yu
2026-07-08 10:15 ` sashiko-bot
2026-07-09 7:49 ` Krzysztof Kozlowski
2026-07-08 10:02 ` [PATCH v8 3/7] clk: qcom: Add generic clkref_en support Qiang Yu
2026-07-08 10:27 ` sashiko-bot
2026-07-08 10:02 ` [PATCH v8 4/7] clk: qcom: tcsrcc-glymur: Add regulator supplies and migrate to clk_ref helper Qiang Yu
2026-07-08 10:02 ` [PATCH v8 5/7] clk: qcom: tcsrcc-glymur: Add Mahua QREF regulator support Qiang Yu
2026-07-08 10:39 ` sashiko-bot [this message]
2026-07-09 11:24 ` Konrad Dybcio
2026-07-08 10:02 ` [PATCH v8 6/7] arm64: dts: qcom: glymur: Add QREF regulator supplies to TCSR Qiang Yu
2026-07-08 10:02 ` [PATCH v8 7/7] arm64: dts: qcom: mahua: " 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=20260708103911.470351F000E9@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