* [PATCH v2 1/1] arm64: dts: qcom: ipq6018: fix clock rates for GCC_USB0_MOCK_UTMI_CLK
@ 2023-12-03 15:40 Chukun Pan
2023-12-03 16:33 ` Krzysztof Kozlowski
0 siblings, 1 reply; 5+ messages in thread
From: Chukun Pan @ 2023-12-03 15:40 UTC (permalink / raw)
To: Bjorn Andersson
Cc: Andy Gross, Konrad Dybcio, Krzysztof Kozlowski, Conor Dooley,
Rob Herring, linux-arm-msm, linux-kernel, devicetree, Chukun Pan
The clock provided by XO is 24MHz, not 20MHz.
Fixes: 5726079cd486 ("arm64: dts: ipq6018: Use reference clock to set dwc3 period")
Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
---
Changes in v2:
* No changes, resend due to error link to other threads.
arch/arm64/boot/dts/qcom/ipq6018.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/qcom/ipq6018.dtsi b/arch/arm64/boot/dts/qcom/ipq6018.dtsi
index 2399d16f147e..d114c8096347 100644
--- a/arch/arm64/boot/dts/qcom/ipq6018.dtsi
+++ b/arch/arm64/boot/dts/qcom/ipq6018.dtsi
@@ -621,7 +621,7 @@ usb3: usb@8af8800 {
<&gcc GCC_USB0_MOCK_UTMI_CLK>;
assigned-clock-rates = <133330000>,
<133330000>,
- <20000000>;
+ <24000000>;
resets = <&gcc GCC_USB0_BCR>;
status = "disabled";
--
2.25.1
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH v2 1/1] arm64: dts: qcom: ipq6018: fix clock rates for GCC_USB0_MOCK_UTMI_CLK
2023-12-03 15:40 [PATCH v2 1/1] arm64: dts: qcom: ipq6018: fix clock rates for GCC_USB0_MOCK_UTMI_CLK Chukun Pan
@ 2023-12-03 16:33 ` Krzysztof Kozlowski
2023-12-05 3:02 ` Chukun Pan
0 siblings, 1 reply; 5+ messages in thread
From: Krzysztof Kozlowski @ 2023-12-03 16:33 UTC (permalink / raw)
To: Chukun Pan, Bjorn Andersson
Cc: Andy Gross, Konrad Dybcio, Krzysztof Kozlowski, Conor Dooley,
Rob Herring, linux-arm-msm, linux-kernel, devicetree
On 03/12/2023 16:40, Chukun Pan wrote:
> The clock provided by XO is 24MHz, not 20MHz.
That does not look like XO, but GCC_USB0_MOCK_UTMI_CLK
>
> Fixes: 5726079cd486 ("arm64: dts: ipq6018: Use reference clock to set dwc3 period")
> Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH v2 1/1] arm64: dts: qcom: ipq6018: fix clock rates for GCC_USB0_MOCK_UTMI_CLK
2023-12-03 16:33 ` Krzysztof Kozlowski
@ 2023-12-05 3:02 ` Chukun Pan
2023-12-05 7:02 ` Krzysztof Kozlowski
0 siblings, 1 reply; 5+ messages in thread
From: Chukun Pan @ 2023-12-05 3:02 UTC (permalink / raw)
To: krzysztof.kozlowski
Cc: agross, amadeus, andersson, conor+dt, devicetree, konrad.dybcio,
krzysztof.kozlowski+dt, linux-arm-msm, linux-kernel, robh+dt
> That does not look like XO, but GCC_USB0_MOCK_UTMI_CLK
I don't have the datasheet, but the reference clock (XO) is 24MHz,
and I receive the following warning:
clk: couldn't set gcc_usb0_mock_utmi_clk clk rate to 20000000 (-22), current rate: 24000000
Thanks,
Chukun
--
2.25.1
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH v2 1/1] arm64: dts: qcom: ipq6018: fix clock rates for GCC_USB0_MOCK_UTMI_CLK
2023-12-05 3:02 ` Chukun Pan
@ 2023-12-05 7:02 ` Krzysztof Kozlowski
2023-12-06 3:01 ` Chukun Pan
0 siblings, 1 reply; 5+ messages in thread
From: Krzysztof Kozlowski @ 2023-12-05 7:02 UTC (permalink / raw)
To: Chukun Pan
Cc: agross, andersson, conor+dt, devicetree, konrad.dybcio,
krzysztof.kozlowski+dt, linux-arm-msm, linux-kernel, robh+dt
On 05/12/2023 04:02, Chukun Pan wrote:
>> That does not look like XO, but GCC_USB0_MOCK_UTMI_CLK
>
> I don't have the datasheet, but the reference clock (XO) is 24MHz,
> and I receive the following warning:
> clk: couldn't set gcc_usb0_mock_utmi_clk clk rate to 20000000 (-22), current rate: 24000000
Referencing XO in commit msg is confusing. Anyway, answer to such error
is not necessarily change the clock rate. What if it must be 20 MHz? You
just ignore such requirement...
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH v2 1/1] arm64: dts: qcom: ipq6018: fix clock rates for GCC_USB0_MOCK_UTMI_CLK
2023-12-05 7:02 ` Krzysztof Kozlowski
@ 2023-12-06 3:01 ` Chukun Pan
0 siblings, 0 replies; 5+ messages in thread
From: Chukun Pan @ 2023-12-06 3:01 UTC (permalink / raw)
To: krzysztof.kozlowski
Cc: agross, amadeus, andersson, conor+dt, devicetree, konrad.dybcio,
krzysztof.kozlowski+dt, linux-arm-msm, linux-kernel, robh+dt
> Referencing XO in commit msg is confusing. Anyway, answer to such error
> is not necessarily change the clock rate. What if it must be 20 MHz? You
> just ignore such requirement..
The downstream QSDK kernel [1] and GCC_USB1_MOCK_UTMI_CLK are both 24MHz.
Judging from these commit [1][2], I think they forgot to make changes here.
1. https://git.codelinaro.org/clo/qsdk/oss/kernel/linux-ipq-5.4/-/commit/486c8485f59
2. https://github.com/torvalds/linux/commit/d1c10ab1494f09eb12fa6e58fc78bb28d44922ae
Thanks,
Chukun
--
2.25.1
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-12-06 3:01 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-12-03 15:40 [PATCH v2 1/1] arm64: dts: qcom: ipq6018: fix clock rates for GCC_USB0_MOCK_UTMI_CLK Chukun Pan
2023-12-03 16:33 ` Krzysztof Kozlowski
2023-12-05 3:02 ` Chukun Pan
2023-12-05 7:02 ` Krzysztof Kozlowski
2023-12-06 3:01 ` Chukun Pan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).