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] [day] [month] [year] [list]

Message-Id: <20231206030108.183402-1-amadeus@jmu.edu.cn>
Date:   Wed,  6 Dec 2023 11:01:08 +0800
From:   Chukun Pan <amadeus@....edu.cn>
To:     krzysztof.kozlowski@...aro.org
Cc:     agross@...nel.org, amadeus@....edu.cn, 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

> 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