All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Zapolskiy <vz@kernel.org>
To: Loic Poulain <loic.poulain@oss.qualcomm.com>,
	Robert Foss <rfoss@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Abel Vesa <abelvesa@kernel.org>
Cc: Andi Shyti <andi.shyti@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: [PATCH 0/3] arm64: dts: qcom: sm8350: Add CCI and camera MCLK pins
Date: Thu,  5 Nov 2026 01:05:26 +0200	[thread overview]
Message-ID: <20261104230529.3040285-1-vz@kernel.org> (raw)

Add Qualcomm SM8350 Camera Control Interface (CCI) controllers and the
pin configurations of camera sensor master clock outputs.

The series depends on the SM8350 camera clock controller support:

  https://lore.kernel.org/all/20261104001704.2744766-1-vz@kernel.org/

Vladimir Zapolskiy (3):
  dt-bindings: i2c: qcom-cci: Document SM8350 compatible
  arm64: dts: qcom: sm8350: Add CCI device tree nodes
  arm64: dts: qcom: sm8350: Add camera MCLK pinctrl states

 .../devicetree/bindings/i2c/qcom,i2c-cci.yaml |   2 +
 arch/arm64/boot/dts/qcom/sm8350.dtsi          | 231 ++++++++++++++++++
 2 files changed, 233 insertions(+)

-- 
2.51.0


             reply	other threads:[~2026-11-04 23:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 23:05 Vladimir Zapolskiy [this message]
2026-11-04 23:05 ` [PATCH 1/3] dt-bindings: i2c: qcom-cci: Document SM8350 compatible Vladimir Zapolskiy
2026-11-05  8:38   ` Loic Poulain
2026-11-07 14:27   ` Wolfram Sang
2026-11-04 23:05 ` [PATCH 2/3] arm64: dts: qcom: sm8350: Add CCI device tree nodes Vladimir Zapolskiy
2026-11-05  8:37   ` Loic Poulain
2026-11-07 18:12     ` Vladimir Zapolskiy
2026-11-09  8:46       ` Loic Poulain
2026-11-04 23:05 ` [PATCH 3/3] arm64: dts: qcom: sm8350: Add camera MCLK pinctrl states Vladimir Zapolskiy
2026-11-05  8:56   ` Konrad Dybcio

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=20261104230529.3040285-1-vz@kernel.org \
    --to=vz@kernel.org \
    --cc=abelvesa@kernel.org \
    --cc=andersson@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=loic.poulain@oss.qualcomm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.