linux-kernel - Re: [PATCH v2 1/1] arm64: dts: qcom: ipq6018: fix clock rates for GCC_USB0_MOCK_UTMI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <64ea0631-13d9-4661-bf83-05ef21a1611d@linaro.org>
Date:   Tue, 5 Dec 2023 08:02:59 +0100
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Chukun Pan <amadeus@....edu.cn>
Cc:     agross@...nel.org, andersson@...nel.org, conor+dt@...nel.org,
        devicetree@...r.kernel.org, konrad.dybcio@...aro.org,
        krzysztof.kozlowski+dt@...aro.org, linux-arm-msm@...r.kernel.org,
        linux-kernel@...r.kernel.org, robh+dt@...nel.org
Subject: Re: [PATCH v2 1/1] arm64: dts: qcom: ipq6018: fix clock rates for
 GCC_USB0_MOCK_UTMI_CLK

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