Devicetree
 help / color / mirror / Atom feed
From: Vladimir Zapolskiy <vz@kernel.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Loic Poulain <loic.poulain@oss.qualcomm.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>
Cc: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Abel Vesa <abelvesa@kernel.org>,
	linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: [PATCH 0/4] media: qcom: camss: Add SM8350 CAMSS support
Date: Thu,  5 Nov 2026 01:45:29 +0200	[thread overview]
Message-ID: <20261104234533.3044265-1-vz@kernel.org> (raw)

Add support of the camera subsystem (CAMSS) found on Qualcomm SM8350
SoC containing:
* three CSID and two CSID lite blocks,
* three VFE and two VFE lite blocks.

The SM8350 CSID and VFE block are programmed like on SM8250.

The series depends on the SM8350 camera clock controller support and
on the change from SM8450 CAMSS series, which allows CSI2 PHY devices
without CSIPHY resources:

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

SM8350 CSIPHYs are described as separate CSI2 PHY devices, and their
support will be added separately along with their connection to
the CAMSS input ports.

Tested on SM8350-HDK with the CSID internal test pattern generator,
the GCC camera HF AXI and the IFE lite AXI clocks are described in the
device tree bindings, but apparently they are not needed to stream
from TPG:

  media-ctl -d /dev/media0 -r
  media-ctl -d /dev/media0 -l '"msm_csid0":1->"msm_vfe0_rdi0":0[1]'
  media-ctl -d /dev/media0 \
      -V '"msm_csid0":0[fmt:SRGGB10_1X10/1920x1080 field:none]'
  media-ctl -d /dev/media0 \
      -V '"msm_vfe0_rdi0":0[fmt:SRGGB10_1X10/1920x1080 field:none]'
  CSID0=$(media-ctl -d /dev/media0 -e msm_csid0)
  VID0=$(media-ctl -d /dev/media0 -e msm_vfe0_video0)
  v4l2-ctl -d $CSID0 -c test_pattern=9
  yavta -B capture-mplane -c10 -n5 -I -f SRGGB10P -s 1920x1080 -F $VID0

Vladimir Zapolskiy (4):
  dt-bindings: media: Add Qualcomm SM8350 CAMSS
  media: qcom: camss: Select Titan 480 CSID offset by VFE type
  media: qcom: camss: Add SM8350 CAMSS support
  arm64: dts: qcom: sm8350: Add CAMSS device tree node

 .../bindings/media/qcom,sm8350-camss.yaml     | 262 ++++++++++++++++++
 arch/arm64/boot/dts/qcom/sm8350.dtsi          | 110 ++++++++
 .../media/platform/qcom/camss/camss-csid.c    |   5 +-
 drivers/media/platform/qcom/camss/camss-vfe.c |   2 +
 drivers/media/platform/qcom/camss/camss.c     | 213 ++++++++++++++
 drivers/media/platform/qcom/camss/camss.h     |   1 +
 6 files changed, 591 insertions(+), 2 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/media/qcom,sm8350-camss.yaml

-- 
2.51.0


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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 23:45 Vladimir Zapolskiy [this message]
2026-11-04 23:45 ` [PATCH 1/4] dt-bindings: media: Add Qualcomm SM8350 CAMSS Vladimir Zapolskiy
2026-11-05  9:54   ` Bryan O'Donoghue
2026-11-05 11:13   ` Krzysztof Kozlowski
2026-11-04 23:45 ` [PATCH 2/4] media: qcom: camss: Select Titan 480 CSID offset by VFE type Vladimir Zapolskiy
2026-11-05  9:51   ` Bryan O'Donoghue
2026-11-04 23:45 ` [PATCH 3/4] media: qcom: camss: Add SM8350 CAMSS support Vladimir Zapolskiy
2026-11-05  9:53   ` Bryan O'Donoghue
2026-11-04 23:45 ` [PATCH 4/4] arm64: dts: qcom: sm8350: Add CAMSS device tree node Vladimir Zapolskiy
2026-11-05  9:56   ` Bryan O'Donoghue

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=20261104234533.3044265-1-vz@kernel.org \
    --to=vz@kernel.org \
    --cc=abelvesa@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bryan.odonoghue@linaro.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-media@vger.kernel.org \
    --cc=loic.poulain@oss.qualcomm.com \
    --cc=mchehab@kernel.org \
    --cc=robh@kernel.org \
    --cc=vladimir.zapolskiy@linaro.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