diff options
| author | Loic Poulain <loic.poulain@oss.qualcomm.com> | 2026-09-29 14:25:45 +0200 |
|---|---|---|
| committer | Andi Shyti <andi.shyti@kernel.org> | 2026-10-04 16:32:26 +0200 |
| commit | d07c7775ca17c4123164806d6210f22dd62cef4f (patch) | |
| tree | 6402818f371e9f1245177f2d13b45ce0081bb019 /tools/lib/python | |
| parent | 8027cc6835c7b4546a88c09e1a871bbf4e780000 (diff) | |
| download | linux-next-d07c7775ca17c4123164806d6210f22dd62cef4f.tar.gz linux-next-d07c7775ca17c4123164806d6210f22dd62cef4f.zip | |
i2c: qcom-cci: Switch msm8953 to the CCI v2 timing/rate config
The msm8953 CCI timing table is internally inconsistent. Its Standard
and Fast timings match v1/v1.5, which are calibrated for a 19.2 MHz CCI
clock, but its Fast+ timings are essentially the 'v2' values, which are
calibrated for 37.5 MHz. Since all masters share a single CCI clock,
no single rate can satisfy all three modes with the current table, and
the DT assigns 19.2 MHz, so Fast+ timings are wrong.
The msm8953 CCI is the same hardware version as msm8996/sdm630, which
already use the cci_v2_data config (37.5 MHz). 37.5 MHz is supported by
the msm8953 CCI RCG, so reuse cci_v2_data for msm8953 as well and drop
the redundant, inconsistent standalone table. This makes all three I2C
modes self-consistent under a single clock rate.
Note this requires the CCI clock to run at 37.5 MHz, the driver selects
and enforces the proper rate in following patches.
Signed-off-by: Loic Poulain <loic.poulain@oss.qualcomm.com>
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Reviewed-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Signed-off-by: Andi Shyti <andi.shyti@kernel.org>
Link: https://patch.msgid.link/20260929-cci-clk-fix-v6-1-62a268cccb0f@oss.qualcomm.com
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions
