From: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
To: Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
Robert Foss <rfoss@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>
Cc: mfd@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-i2c@vger.kernel.org, vikram.sharma@oss.qualcomm.com,
nihal.gupta@oss.qualcomm.com, vtumati@quicinc.com,
bryan.odonoghue@linaro.org,
Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
Subject: [PATCH RFC 2/3] dt-bindings: i2c: qcom-cci: Document Nord compatible
Date: Thu, 05 Nov 2026 19:11:00 +0800 [thread overview]
Message-ID: <20261105-ccu-v1-2-3accc4b901de@oss.qualcomm.com> (raw)
In-Reply-To: <20261105-ccu-v1-0-3accc4b901de@oss.qualcomm.com>
Add the Nord CCI compatible. The CCI is based on the CCI v2 core, but
is wrapped by a CCU. After reset, the I2C ports are routed to the CCU
and the CCU output mux must select the CCI before any transfer can
take place.
Add the qcom,ccu-mux-sel property to describe the syscon register and
bits controlling the CCU output mux.
In addition to its core clock, the CCI requires the CCU AHB clock and
the camera subsystem top AHB and fast AHB clocks. The top AHB clock is
required to access the CCI registers and the CCU output mux.
Signed-off-by: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
---
.../devicetree/bindings/i2c/qcom,i2c-cci.yaml | 41 ++++++++++++++++++++++
1 file changed, 41 insertions(+)
diff --git a/Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml b/Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml
index 1e8def25ec0ec1ef6b34859709d10a2a36fe36f5..5a25ebe0e61f686b86306a1dc94911e302d9b440 100644
--- a/Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml
+++ b/Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml
@@ -29,6 +29,7 @@ properties:
- qcom,glymur-cci
- qcom,kaanapali-cci
- qcom,milos-cci
+ - qcom,nord-cci
- qcom,qcm2290-cci
- qcom,qcs8300-cci
- qcom,sa8775p-cci
@@ -70,6 +71,20 @@ properties:
reg:
maxItems: 1
+ qcom,ccu-mux-sel:
+ $ref: /schemas/types.yaml#/definitions/phandle-array
+ description:
+ On SoCs where the CCI sits in a CCU wrapper, the CCI I2C ports are
+ routed to the CCU after reset and the CCU output mux has to select the
+ CCI before any transfer.
+ items:
+ - items:
+ - description: phandle to the Titan CAM_TOP syscon
+ - description: byte offset of the CCU output mux register in the
+ syscon
+ - description: mask of the mux bits of this CCI, set to 1 to route
+ the I2C ports to this CCI
+
patternProperties:
"^i2c-bus@[01]$":
$ref: /schemas/i2c/i2c-controller.yaml#
@@ -131,6 +146,32 @@ allOf:
- const: cci_ahb
- const: cci
+ - if:
+ properties:
+ compatible:
+ contains:
+ const: qcom,nord-cci
+ then:
+ properties:
+ clocks:
+ items:
+ - description: Camera subsystem top AHB clock, needed by the CCI
+ register interface and to access the CCU output mux
+ - description: CCI core clock
+ - description: AHB clock of the CCU wrapper the CCI sits in
+ - description: Camera subsystem top fast AHB clock
+ clock-names:
+ items:
+ - const: ahb
+ - const: cci
+ - const: ccu_ahb
+ - const: fast_ahb
+ required:
+ - qcom,ccu-mux-sel
+ else:
+ properties:
+ qcom,ccu-mux-sel: false
+
- if:
properties:
compatible:
--
2.34.1
next prev parent reply other threads:[~2026-11-05 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 11:10 [PATCH RFC 0/3] Support the Nord CCI CCU output mux Wenmeng Liu
2026-11-05 11:10 ` [PATCH RFC 1/3] dt-bindings: mfd: syscon: Add Qualcomm Nord Titan CAM_TOP Wenmeng Liu
2026-11-05 11:11 ` Wenmeng Liu [this message]
2026-11-05 11:11 ` [PATCH RFC 3/3] i2c: qcom-cci: Support the CCU output mux Wenmeng Liu
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=20261105-ccu-v1-2-3accc4b901de@oss.qualcomm.com \
--to=wenmeng.liu@oss.qualcomm.com \
--cc=andi.shyti@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@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=mfd@lists.linux.dev \
--cc=nihal.gupta@oss.qualcomm.com \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=vikram.sharma@oss.qualcomm.com \
--cc=vtumati@quicinc.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®