Re: [PATCH] i2c: qcom-cci: skip core clock rates the clock cannot provide

From: Andi Shyti

Date: Sat Oct 10 2026 - 09:48:19 EST


Hi Oleg,

On Fri, Oct 09, 2026 at 01:07:25AM +0200, Oleg Keri wrote:
> cci_get_required_rate() picks the lowest rate that has timings for every
> active master, but never checks that the CCI clock can run at it. On
> glymur, sm8750 and kaanapali the CCI clock table has no 19.2 MHz entry,
> so the request rounds up to 30 MHz or 37.5 MHz, the timing lookup for
> the running rate fails and the controller does not probe:
>
> i2c-qcom-cci ac16000.cci: CCI clock is not at expected 19200000 Hz
> i2c-qcom-cci ac16000.cci: no timing for mode 1 at CCI clock 30000000 Hz
> i2c-qcom-cci ac16000.cci: probe with driver i2c-qcom-cci failed with error -95
>
> Only consider rates clk_round_rate() can deliver exactly. Glymur then
> runs its CCI at 37.5 MHz, which has timings for every mode.
>
> Fixes: fa1eb3af12fa ("i2c: qcom-cci: Enforce the required CCI clock rate")
> Signed-off-by: Oleg Keri <okerixx@xxxxxxxxx>

pushed to i2c/i2c.

Thanks,
Andi

Attachment: signature.asc
Description: PGP signature