From: David Heidelberg <david@ixit.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.

Signed-off-by: David Heidelberg <david@ixit.cz>
---
 arch/arm64/boot/dts/qcom/sdm845-oneplus-enchilada.dts | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/arm64/boot/dts/qcom/sdm845-oneplus-enchilada.dts b/arch/arm64/boot/dts/qcom/sdm845-oneplus-enchilada.dts
index a259eb9d45ae0..881d0f3ebca31 100644
--- a/arch/arm64/boot/dts/qcom/sdm845-oneplus-enchilada.dts
+++ b/arch/arm64/boot/dts/qcom/sdm845-oneplus-enchilada.dts
@@ -41,6 +41,8 @@ &bq27441_fg {
 };
 
 &i2c4 {
+	clock-frequency = <100000>;
+
 	status = "okay";
 
 	max98927_codec: max98927@3a {

---
base-commit: 7d31f578f3230f3b7b33b0930b08f9afd8429817
change-id: 20251130-enchilada-i2c-freq-aca7fae1c70f

Best regards,
-- 
David Heidelberg <david@ixit.cz>

On Sun, 30 Nov 2025 00:22:39 +0100, David Heidelberg wrote:
> 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.
> 
> [...]

Applied, thanks!

[1/1] arm64: dts: qcom: oneplus-enchilada: Specify i2c4 clock frequency
      commit: 1ef28ee5c51f21bc3ff493dfdc175827bbabf195

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

On 11/30/25 12:22 AM, David Heidelberg via B4 Relay wrote:
> From: David Heidelberg <david@ixit.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