Re: [PATCH] arm64: dts: qcom: eliza: Connect USB3 PHY pipe clock to GCC

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Incorrect macro used for a clock specifier in devicetree (PHY ID used instead of clock ID).
--

--- Patch [1]: [PATCH] arm64: dts: qcom: eliza: Connect USB3 PHY pipe clock to GCC ---
commit d454bba6f2028b4ff89f276f88a76156819977d9
Author: Abel Vesa <abel.vesa@oss.qualcomm.com>

arm64: dts: qcom: eliza: Connect USB3 PHY pipe clock to GCC

This commit connects the QMP PHY USB3 output to the GCC clock controller
so the USB3 PHY pipe clock can propagate to the USB controller.

> diff --git a/arch/arm64/boot/dts/qcom/eliza.dtsi b/arch/arm64/boot/dts/qcom/eliza.dtsi
> index 66ea4aaafd73a..2e0fbbfcc47d3 100644
> --- a/arch/arm64/boot/dts/qcom/eliza.dtsi
> +++ b/arch/arm64/boot/dts/qcom/eliza.dtsi
> @@ -655,7 +655,7 @@ gcc: clock-controller@100000 {
>  				 <&ufs_mem_phy 0>,
>  				 <&ufs_mem_phy 1>,
>  				 <&ufs_mem_phy 2>,
> -				 <0>;
> +				 <&usb_dp_qmpphy QMP_USB43DP_USB3_PHY>;

[Severity: Low]
Does this use the correct macro for a clock specifier?

It looks like the PHY ID macro QMP_USB43DP_USB3_PHY is being used here
instead of the clock ID macro QMP_USB43DP_USB3_PIPE_CLK. While both macros
currently evaluate to 0 and might not cause functional issues right now,
using a PHY ID for a clock reference makes the device tree fragile to
future macro changes and violates the expected bindings.

>  
>  			power-domains = <&rpmhpd RPMHPD_CX>;
>

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260825-dts-qcom-eliza-add-missing-usb-dp-phy-clk-to-gcc-v1-1-f0d3719f798c@oss.qualcomm.com?part=1