From: Loic Poulain <loic.poulain@oss.qualcomm.com>
To: Robert Foss <rfoss@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Luca Weiss <luca@lucaweiss.eu>
Cc: linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, vladimir.zapolskiy@linaro.org,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: [PATCH v2 3/3] i2c: qcom-cci: Fix CCI clock rate enforcement
Date: Mon, 27 Jul 2026 11:21:34 +0200 [thread overview]
Message-ID: <20260727-cci-clk-fix-v2-3-c3958f28b045@oss.qualcomm.com> (raw)
In-Reply-To: <20260727-cci-clk-fix-v2-0-c3958f28b045@oss.qualcomm.com>
The hw_params timing values (thigh, tlow, etc.) are in CCI clock ticks
and were calibrated for a specific clock rate per hardware variant. If
the clock is running at a different rate the I2C timings will be wrong,
potentially violating the I2C specification.
Rather than just warning about a mismatch like before, actively set
the clock to the expected rate, using the OPP framework so that boards
which (will) describe an opp table also get the required power-domain and
regulator votes for that rate. The OPP table is optional, boards without
one simply fall back to a plain clk_set_rate() behavior, so existing DTs
keep working.
Tested-by: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
Suggested-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Signed-off-by: Loic Poulain <loic.poulain@oss.qualcomm.com>
---
drivers/i2c/busses/i2c-qcom-cci.c | 49 +++++++++++++++++++++++++++++++++++++++
1 file changed, 49 insertions(+)
diff --git a/drivers/i2c/busses/i2c-qcom-cci.c b/drivers/i2c/busses/i2c-qcom-cci.c
index 2ed58b2a2f31c62ee1c972a53b71f86787144b84..87d64e308a8152b99ff4cfb4255e24edfb751e75 100644
--- a/drivers/i2c/busses/i2c-qcom-cci.c
+++ b/drivers/i2c/busses/i2c-qcom-cci.c
@@ -11,6 +11,7 @@
#include <linux/of.h>
#include <linux/platform_device.h>
#include <linux/pm_runtime.h>
+#include <linux/pm_opp.h>
#define CCI_HW_VERSION 0x0
#define CCI_RESET_CMD 0x004
@@ -128,6 +129,7 @@ struct cci {
const struct cci_data *data;
struct clk_bulk_data *clocks;
int nclocks;
+ struct clk *cci_clk;
struct cci_master master[NUM_MASTERS];
};
@@ -472,10 +474,35 @@ static void cci_disable_clocks(struct cci *cci)
clk_bulk_disable_unprepare(cci->nclocks, cci->clocks);
}
+static int cci_set_core_rate(struct cci *cci, unsigned long rate)
+{
+ struct device *dev = cci->dev;
+ int ret;
+
+ ret = dev_pm_opp_set_rate(dev, rate);
+ if (ret) {
+ dev_warn(dev, "CCI clock could not be set to %lu Hz\n", rate);
+ return ret;
+ }
+
+ if (!rate)
+ return 0;
+
+ /*
+ * The hw_params timings are only valid at the expected rate,
+ * so verify what actually landed on the hardware.
+ */
+ if (clk_get_rate(cci->cci_clk) != rate)
+ dev_warn(dev, "CCI clock is not at expected %lu Hz\n", rate);
+
+ return 0;
+}
+
static int __maybe_unused cci_suspend_runtime(struct device *dev)
{
struct cci *cci = dev_get_drvdata(dev);
+ cci_set_core_rate(cci, 0);
cci_disable_clocks(cci);
return 0;
}
@@ -485,6 +512,10 @@ static int __maybe_unused cci_resume_runtime(struct device *dev)
struct cci *cci = dev_get_drvdata(dev);
int ret;
+ ret = cci_set_core_rate(cci, cci->data->cci_clk_rate);
+ if (ret)
+ return ret;
+
ret = cci_enable_clocks(cci);
if (ret)
return ret;
@@ -587,6 +618,24 @@ static int cci_probe(struct platform_device *pdev)
return dev_err_probe(dev, -EINVAL, "not enough clocks in DT\n");
cci->nclocks = ret;
+ cci->cci_clk = devm_clk_get(dev, "cci");
+ if (IS_ERR(cci->cci_clk))
+ return dev_err_probe(dev, PTR_ERR(cci->cci_clk),
+ "failed to get CCI clock\n");
+
+ ret = devm_pm_opp_set_clkname(dev, "cci");
+ if (ret)
+ return dev_err_probe(dev, ret, "failed to set CCI OPP clk\n");
+
+ /* OPP table is optional */
+ ret = devm_pm_opp_of_add_table(dev);
+ if (ret && ret != -ENODEV)
+ return dev_err_probe(dev, ret, "failed to add OPP table\n");
+
+ ret = cci_set_core_rate(cci, cci->data->cci_clk_rate);
+ if (ret)
+ return dev_err_probe(dev, ret, "failed to set CCI clock rate\n");
+
ret = cci_enable_clocks(cci);
if (ret < 0)
return ret;
--
2.34.1
next prev parent reply other threads:[~2026-07-27 9:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 9:21 [PATCH v2 0/3] " Loic Poulain
2026-07-27 9:21 ` [PATCH v2 1/3] i2c: qcom-cci: Switch msm8953 to the CCI v2 timing/rate config Loic Poulain
2026-07-27 19:21 ` Vladimir Zapolskiy
2026-07-28 8:20 ` Loic Poulain
2026-07-28 9:38 ` Vladimir Zapolskiy
2026-07-28 10:26 ` Loic Poulain
2026-07-29 11:40 ` Vladimir Zapolskiy
2026-07-27 9:21 ` [PATCH v2 2/3] Revert "i2c: qcom-cci: Remove unused struct member cci_clk_rate" Loic Poulain
2026-07-27 9:21 ` Loic Poulain [this message]
2026-07-27 9:33 ` [PATCH v2 3/3] i2c: qcom-cci: Fix CCI clock rate enforcement Mukesh Savaliya
2026-07-27 9:45 ` Loic Poulain
2026-07-27 9:50 ` Mukesh Savaliya
2026-07-28 15:57 ` Vladimir Zapolskiy
2026-07-29 11:35 ` Loic Poulain
2026-07-29 11:51 ` Vladimir Zapolskiy
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=20260727-cci-clk-fix-v2-3-c3958f28b045@oss.qualcomm.com \
--to=loic.poulain@oss.qualcomm.com \
--cc=andi.shyti@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--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=luca@lucaweiss.eu \
--cc=rfoss@kernel.org \
--cc=vladimir.zapolskiy@linaro.org \
--cc=wenmeng.liu@oss.qualcomm.com \
--cc=wsa+renesas@sang-engineering.com \
/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®