From: sashiko-bot@kernel.org
To: "Bartosz Golaszewski" <bartosz.golaszewski@oss.qualcomm.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org,
krzk+dt@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: clock: qcom: add missing definition for the USB2 PHY reset
Date: Thu, 14 May 2026 06:04:33 +0000 [thread overview]
Message-ID: <20260514060433.D8C5CC2BCC6@smtp.kernel.org> (raw)
In-Reply-To: <20260513-nord-clk-usb2-phy-v1-1-8eafcb2d5129@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The newly added reset macro is incorrectly named `NE_GCC_QUSB3PHY_PRIM_BCR` instead of `NE_GCC_QUSB2PHY_PRIM_BCR`, contradicting the commit message.
--
commit 995687d91ac26d49f12e0c08bcd404ce73e33d6c
Author: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
dt-bindings: clock: qcom: add missing definition for the USB2 PHY reset
This commit adds the missing USB2 PHY reset definition to the nord-negcc
clock bindings header. This provides the definition needed to add the USB
nodes in the device tree.
> diff --git a/include/dt-bindings/clock/qcom,nord-negcc.h b/include/dt-bindings/clock/qcom,nord-negcc.h
> index 95f333d8e1aa7..c2d048d9fc9e9 100644
> --- a/include/dt-bindings/clock/qcom,nord-negcc.h
> +++ b/include/dt-bindings/clock/qcom,nord-negcc.h
[ ... ]
> @@ -120,5 +120,6 @@
> #define NE_GCC_USB3_PHY_SEC_BCR 10
> #define NE_GCC_USB3PHY_PHY_PRIM_BCR 11
> #define NE_GCC_USB3PHY_PHY_SEC_BCR 12
> +#define NE_GCC_QUSB3PHY_PRIM_BCR 13
The commit message indicates this patch adds the USB2 PHY reset definition,
but the introduced macro is named NE_GCC_QUSB3PHY_PRIM_BCR.
Is this a typo? Should the macro be named NE_GCC_QUSB2PHY_PRIM_BCR to reflect
a USB2 PHY rather than a USB3 PHY before it becomes locked into the
dt-bindings API?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260513-nord-clk-usb2-phy-v1-0-8eafcb2d5129@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-05-14 6:04 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 [this message]
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
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=20260514060433.D8C5CC2BCC6@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