Re: [PATCH] arm64: dts: qcom: hamoa: Fix clocks for HSPHYs

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch assigns the `TCSR_USB2_2_CLKREF_EN` clock to `usb_1_ss2_hsphy` (the tertiary controller's PHY). However, `usb_2_hsphy` (a separate PHY at 0x088e0000) is already assigned this exact same clock reference. This creates a hardware description conflict where two distinct PHYs share a single toggle, contradicting the commit message's claim that the tertiary PHY has its "own toggle".
--

commit 91799d7f574ab3aadbfd7f8695e82875347063f5
Author: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

arm64: dts: qcom: hamoa: Fix clocks for HSPHYs

This commit updates the clock references for the primary and tertiary HSPHYs
on hamoa. The primary PHY is wired directly to the XO clock, and the
tertiary PHY is updated to use TCSR_USB2_2_CLKREF_EN.

> diff --git a/arch/arm64/boot/dts/qcom/hamoa.dtsi b/arch/arm64/boot/dts/qcom/hamoa.dtsi
> --- a/arch/arm64/boot/dts/qcom/hamoa.dtsi
> +++ b/arch/arm64/boot/dts/qcom/hamoa.dtsi
[ ... ]
> @@ -3010,7 +3010,7 @@ usb_1_ss2_hsphy: phy@fde000 {
>  			reg = <0 0x00fde000 0 0x154>;
>  			#phy-cells = <0>;
>  
> -			clocks = <&tcsr TCSR_USB2_1_CLKREF_EN>;
> +			clocks = <&tcsr TCSR_USB2_2_CLKREF_EN>;

The commit message notes the tertiary PHY has its "own toggle", but does
assigning TCSR_USB2_2_CLKREF_EN here result in two PHYs sharing a toggle?

It appears that usb_2_hsphy (located at 0x088e0000) is already assigned this
exact same clock reference. If both usb_1_ss2_hsphy and usb_2_hsphy share
TCSR_USB2_2_CLKREF_EN in the device tree, does usb_2_hsphy also need its
clock assignment updated to correctly model the hardware?

>  			clock-names = "ref";
>  
>  			resets = <&gcc GCC_QUSB2PHY_TERT_BCR>;

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260518-topic-hamoa_hsphy_clk-v1-1-d85203756505@oss.qualcomm.com?part=1