From: Richard Acayan <mailingradian@gmail.com>
To: Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org
Cc: Richard Acayan <mailingradian@gmail.com>
Subject: [RFC PATCH 0/3] media: qcom: camss: support for empty endpoint nodes
Date: Mon, 29 Dec 2025 21:27:56 -0500 [thread overview]
Message-ID: <20251230022759.9449-1-mailingradian@gmail.com> (raw)
This series adds support for empty endpoint nodes. It is currently RFC
because it continues an ongoing discussion on how to selectively connect
some CAMSS ports to cameras and leave others disconnected.
The SDM670 patches are for a full example. If agreed on, this should
expand to SoCs that have CAMSS.
Example SoC dtsi:
camss: isp@00000000 {
...
status = "disabled";
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
camss_endpoint0: endpoint {
};
};
port@1 {
reg = <1>;
camss_endpoint1: endpoint {
};
};
port@2 {
reg = <2>;
camss_endpoint2: endpoint {
};
};
};
};
Example device dts:
&camss {
status = "okay";
};
&camss_endpoint1 {
clock-lanes = <7>;
data-lanes = <0 1 2 3>;
remote-endpoint = <&cam_front_endpoint>;
};
&cci_i2c1 {
camera@1a {
...
port {
cam_front_endpoint: endpoint {
data-lanes = <1 2 3 4>;
link-frequencies = /bits/ 64 <360000000>;
remote-endpoint = <&camss_endpoint1>;
};
};
};
};
Richard Acayan (3):
dt-bindings: media: camss: sdm670: Make endpoint properties optional
media: qcom: camss: allow endpoints with no remote
arm64: dts: qcom: sdm670: remove status properties of camss endpoints
.../devicetree/bindings/media/qcom,sdm670-camss.yaml | 12 ------------
arch/arm64/boot/dts/qcom/sdm670.dtsi | 3 ---
drivers/media/platform/qcom/camss/camss.c | 5 ++---
3 files changed, 2 insertions(+), 18 deletions(-)
--
2.52.0
next reply other threads:[~2025-12-30 2:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 2:27 Richard Acayan [this message]
2025-12-30 2:27 ` [RFC PATCH 1/3] dt-bindings: media: camss: sdm670: Make endpoint properties optional Richard Acayan
2025-12-30 7:30 ` Krzysztof Kozlowski
2025-12-30 2:27 ` [RFC PATCH 2/3] media: qcom: camss: allow endpoints with no remote Richard Acayan
2025-12-30 2:27 ` [RFC PATCH 3/3] arm64: dts: qcom: sdm670: remove status properties of camss endpoints Richard Acayan
2025-12-30 8:18 ` [RFC PATCH 0/3] media: qcom: camss: support for empty endpoint nodes Vladimir Zapolskiy
2025-12-31 3:02 ` Richard Acayan
2025-12-31 8:34 ` Vladimir Zapolskiy
2026-01-30 11:31 ` Konrad Dybcio
2025-12-30 9:40 ` Bryan O'Donoghue
2025-12-31 2:20 ` Richard Acayan
2025-12-31 3:08 ` Bryan O'Donoghue
2026-01-10 1:03 ` Richard Acayan
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=20251230022759.9449-1-mailingradian@gmail.com \
--to=mailingradian@gmail.com \
--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=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--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