From: Andi Shyti <andi.shyti@kernel.org>
To: Oleg Keri <okerixx@gmail.com>
Cc: Loic Poulain <loic.poulain@oss.qualcomm.com>,
Robert Foss <rfoss@kernel.org>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: qcom-cci: skip core clock rates the clock cannot provide
Date: Sat, 10 Oct 2026 15:45:22 +0200 [thread overview]
Message-ID: <aspA3ZawIVWJ3iLL@zenone.zhora.eu> (raw)
In-Reply-To: <20261008230725.3228-1-okerixx@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
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@gmail.com>
pushed to i2c/i2c.
Thanks,
Andi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-10-10 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 23:07 Oleg Keri
2026-10-09 14:39 ` Loic Poulain
2026-10-10 13:45 ` Andi Shyti [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aspA3ZawIVWJ3iLL@zenone.zhora.eu \
--to=andi.shyti@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=okerixx@gmail.com \
--cc=rfoss@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®