summaryrefslogtreecommitdiff
path: root/tools/lib/python
diff options
context:
space:
mode:
authorLoic Poulain <loic.poulain@oss.qualcomm.com>2026-09-29 14:25:48 +0200
committerAndi Shyti <andi.shyti@kernel.org>2026-10-04 16:32:51 +0200
commit826a1d134c3ea80d6cc2cd763bda7a374ae2be9f (patch)
treeeccf4e4c8ec657b72a409bb065bc5de65d50d574 /tools/lib/python
parent04ec5e09518b2fafe03540a0c93df858be99cefd (diff)
downloadlinux-next-826a1d134c3ea80d6cc2cd763bda7a374ae2be9f.tar.gz
linux-next-826a1d134c3ea80d6cc2cd763bda7a374ae2be9f.zip
i2c: qcom-cci: Share the timing table across CCI revisions
The hw_params timing values only depend on the CCI clock rate and the I2C mode, not on the hardware revision: every per-variant table used identical values for a given [rate][mode]. Only the set of supported modes differs between revisions. Move the timings into a single shared cci_hw_params[rate][mode] table and describe each variant's highest supported mode in cci_data with max_mode instead of duplicating the timing values. This removes the per-variant timing tables without any functional change. Suggested-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org> 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-4-62a268cccb0f@oss.qualcomm.com
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions