devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Dybcio <konradybcio@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
	 Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	 Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	 Loic Poulain <loic.poulain@oss.qualcomm.com>,
	 Robert Foss <rfoss@kernel.org>,
	Andi Shyti <andi.shyti@kernel.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
	 linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
	 Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: [PATCH 0/5] Qualcomm CCI I2C clock requirements enforcement
Date: Thu, 04 Sep 2025 16:31:19 +0200	[thread overview]
Message-ID: <20250904-topic-cci_updates-v1-0-d38559692703@oss.qualcomm.com> (raw)

The hardware requires the faster of the two (37.5 MHz as opposed to
19.2 MHz) clock rates to hit the required timings for I2C Fast+ Mode.

Additionally, the magic presets for electrical tuning registers on SoCs
supporting that faster mode ("cci_v2" in the driver) are calculated
based on that faster frequency.

Moreover, while its unlikely that it would ever exhibit as an issue
given CCI is a slow & tiny core, we do need to express a minimal voltage
level for any given clock rate, which is where the (optional -
backwards compat) OPP table addition comes in.

This series helps ensure all these requirements are met.

Patch 1 is a related but independent fix, can be picked right away
Patch 5 can be functionally merged as-is, but depends on patch 2 for
bindings

Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
---
Konrad Dybcio (5):
      arm64: dts: qcom: sc8280xp: Fix CCI3 interrupt
      dt-bindings: i2c: qcom-cci: Allow operating-points-v2
      i2c: qcom-cci: Drop single-line wrappers
      i2c: qcom-cci: Add OPP table support and enforce FAST_PLUS requirements
      arm64: dts: qcom: sc8280xp: Add OPP table for CCI hosts

 .../devicetree/bindings/i2c/qcom,i2c-cci.yaml      |  2 +
 arch/arm64/boot/dts/qcom/sc8280xp.dtsi             | 16 +++++++-
 drivers/i2c/busses/i2c-qcom-cci.c                  | 45 +++++++++++++++++-----
 3 files changed, 52 insertions(+), 11 deletions(-)
---
base-commit: 4ac65880ebca1b68495bd8704263b26c050ac010
change-id: 20250904-topic-cci_updates-800fdc9bada4

Best regards,
-- 
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>


             reply	other threads:[~2025-09-04 14:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04 14:31 Konrad Dybcio [this message]
2025-09-04 14:31 ` [PATCH 1/5] arm64: dts: qcom: sc8280xp: Fix CCI3 interrupt Konrad Dybcio
2025-09-04 14:35   ` Bryan O'Donoghue
2025-09-04 14:31 ` [PATCH 2/5] dt-bindings: i2c: qcom-cci: Allow operating-points-v2 Konrad Dybcio
2025-09-04 14:50   ` Bryan O'Donoghue
2025-09-05 18:03   ` Rob Herring (Arm)
2025-09-04 14:31 ` [PATCH 3/5] i2c: qcom-cci: Drop single-line wrappers Konrad Dybcio
2025-09-04 14:52   ` Bryan O'Donoghue
2025-09-05  7:40   ` Loic Poulain
2025-09-04 14:31 ` [PATCH 4/5] i2c: qcom-cci: Add OPP table support and enforce FAST_PLUS requirements Konrad Dybcio
2025-09-04 14:50   ` Konrad Dybcio
2025-09-04 14:55   ` Bryan O'Donoghue
2025-09-08  8:36   ` Stephan Gerhold
2025-09-08  8:43     ` Konrad Dybcio
2025-09-08  8:46       ` Stephan Gerhold
2025-09-08  9:49         ` Konrad Dybcio
2025-09-08  9:57           ` Stephan Gerhold
2025-09-08 10:00             ` Konrad Dybcio
2025-09-08 10:09               ` Stephan Gerhold
2025-09-09  8:39                 ` Konrad Dybcio
2025-09-10 10:57   ` Mukesh Savaliya
2025-09-04 14:31 ` [PATCH 5/5] arm64: dts: qcom: sc8280xp: Add OPP table for CCI hosts Konrad Dybcio
2025-09-04 14:56   ` Bryan O'Donoghue
2025-09-10 10:57 ` [PATCH 0/5] Qualcomm CCI I2C clock requirements enforcement Mukesh Savaliya

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=20250904-topic-cci_updates-v1-0-d38559692703@oss.qualcomm.com \
    --to=konradybcio@kernel.org \
    --cc=andersson@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --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=marijn.suijten@somainline.org \
    --cc=rfoss@kernel.org \
    --cc=robh@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;
as well as URLs for NNTP newsgroup(s).