linux-kernel - Re: [PATCH] arm64: dts: qcom: oneplus-enchilada: Specify i2c4 clock frequency

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: <c80db42f-518f-4682-8e43-3fa56fe569f6@oss.qualcomm.com>
Date: Mon, 1 Dec 2025 12:13:49 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: david@...t.cz, Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley <conor+dt@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: oneplus-enchilada: Specify i2c4 clock
 frequency

On 11/30/25 12:22 AM, David Heidelberg via B4 Relay wrote:
> From: David Heidelberg <david@...t.cz>
> 
> Per the binding, omitting the clock frequency from a Geni I2C controller
> node defaults the bus to 100 kHz. But at least in Linux, a friendly info
> print highlights the lack of explicitly defined frequency in the
> DeviceTree.
> 
> Specify the frequency, to give it an explicit value, and to silence the
> log print in Linux.
> 
> Downstream doesn't define any frequency, thus also using 100 kHz.

Could you e.g. run debugcc to check out the frequency of the related
clock to make sure?

https://github.com/linux-msm/debugcc

Konrad