From: sashiko-bot@kernel.org
To: "Bartosz Golaszewski" <bartosz.golaszewski@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org,
krzk+dt@kernel.org
Subject: Re: [PATCH 2/2] clk: qcom: nord: negcc: add missing definition for the USB2 PHY reset
Date: Thu, 14 May 2026 06:16:42 +0000 [thread overview]
Message-ID: <20260514061642.D6B43C2BCB7@smtp.kernel.org> (raw)
In-Reply-To: <20260513-nord-clk-usb2-phy-v1-2-8eafcb2d5129@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The newly introduced UAPI macro for the USB2 PHY reset is incorrectly named `NE_GCC_QUSB3PHY_PRIM_BCR` instead of `NE_GCC_QUSB2PHY_PRIM_BCR`.
--
commit 6d297fb76d38d25ccff03c1716dff37d01275b24
Author: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
clk: qcom: nord: negcc: add missing definition for the USB2 PHY reset
This commit adds the missing USB2 PHY reset definition to the negcc clock
driver and its bindings. This enables adding the USB nodes in the device
tree.
> diff --git a/drivers/clk/qcom/negcc-nord.c b/drivers/clk/qcom/negcc-nord.c
> index 1aa24e2784e53..31442d39924a6 100644
> --- a/drivers/clk/qcom/negcc-nord.c
> +++ b/drivers/clk/qcom/negcc-nord.c
> @@ -1918,6 +1918,7 @@ static const struct qcom_reset_map ne_gcc_nord_resets[] = {
> [NE_GCC_USB3_PHY_SEC_BCR] = { 0x2d000 },
> [NE_GCC_USB3PHY_PHY_PRIM_BCR] = { 0x2b004 },
> [NE_GCC_USB3PHY_PHY_SEC_BCR] = { 0x2d004 },
> + [NE_GCC_QUSB3PHY_PRIM_BCR] = { 0x2e000 },
Should this be NE_GCC_QUSB2PHY_PRIM_BCR instead of NE_GCC_QUSB3PHY_PRIM_BCR?
The commit message explicitly states the intention to add the USB2 PHY reset,
and Qualcomm conventions typically use QUSB2 for USB 2.0 PHYs. Since this
macro is part of the device tree bindings, correcting this typo before it
merges will prevent the QUSB3 name from becoming part of the permanent ABI.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260513-nord-clk-usb2-phy-v1-0-8eafcb2d5129@oss.qualcomm.com?part=2
prev parent reply other threads:[~2026-05-14 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 15:35 [PATCH 0/2] clk: qcom: nord: add missing define for the USB2 PHY reset Bartosz Golaszewski
2026-05-13 15:35 ` [PATCH 1/2] dt-bindings: clock: qcom: add missing definition " Bartosz Golaszewski
2026-05-14 6:04 ` sashiko-bot
2026-05-13 15:35 ` [PATCH 2/2] clk: qcom: nord: negcc: " Bartosz Golaszewski
2026-05-13 15:45 ` Bartosz Golaszewski
2026-05-14 6:16 ` 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=20260514061642.D6B43C2BCB7@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--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