From: Richard Acayan <mailingradian@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Bryan O'Donoghue" <bod@kernel.org>,
Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Tianshu Qiu <tian.shu.qiu@intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Cc: Robert Mader <robert.mader@collabora.com>,
David Heidelberg <david@ixit.cz>,
phone-devel@vger.kernel.org,
Richard Acayan <mailingradian@gmail.com>
Subject: [PATCH v11 1/7] dt-bindings: media: qcom,sdm670-camss: Remove clock-lanes requirement
Date: Mon, 23 Mar 2026 22:01:26 -0400 [thread overview]
Message-ID: <20260324020132.8683-2-mailingradian@gmail.com> (raw)
In-Reply-To: <20260324020132.8683-1-mailingradian@gmail.com>
The clock-lanes property has no effect on the hardware configuration, as
of commit 336136e197e2 ("media: dt-bindings: media: camss: Remove
clock-lane property"). Since boards with new camss support can omit the
property, remove it from the required lists.
Signed-off-by: Richard Acayan <mailingradian@gmail.com>
---
Documentation/devicetree/bindings/media/qcom,sdm670-camss.yaml | 3 ---
1 file changed, 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/media/qcom,sdm670-camss.yaml b/Documentation/devicetree/bindings/media/qcom,sdm670-camss.yaml
index 46cc7fff1599..084b65740d53 100644
--- a/Documentation/devicetree/bindings/media/qcom,sdm670-camss.yaml
+++ b/Documentation/devicetree/bindings/media/qcom,sdm670-camss.yaml
@@ -124,7 +124,6 @@ properties:
maxItems: 4
required:
- - clock-lanes
- data-lanes
port@1:
@@ -147,7 +146,6 @@ properties:
maxItems: 4
required:
- - clock-lanes
- data-lanes
port@2:
@@ -170,7 +168,6 @@ properties:
maxItems: 4
required:
- - clock-lanes
- data-lanes
required:
--
2.53.0
next prev parent reply other threads:[~2026-03-24 2:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 2:01 [PATCH v11 0/7] media: i2c: IMX355 for the Pixel 3a Richard Acayan
2026-03-24 2:01 ` Richard Acayan [this message]
2026-03-24 2:01 ` [PATCH v11 2/7] dt-bindings: media: i2c: Add Sony IMX355 Richard Acayan
2026-03-24 2:01 ` [PATCH v11 3/7] media: i2c: imx355: Support devicetree and power management Richard Acayan
2026-03-24 2:01 ` [PATCH v11 4/7] media: i2c: imx355: Restrict data lanes to 4 Richard Acayan
2026-03-24 2:01 ` [PATCH v11 5/7] arm64: dts: qcom: sdm670: label the camss ports instead of endpoints Richard Acayan
2026-03-24 2:01 ` [PATCH v11 6/7] arm64: dts: qcom: sdm670: add camera mclk pins Richard Acayan
2026-03-24 2:01 ` [PATCH v11 7/7] arm64: dts: qcom: sdm670-google-sargo: add imx355 front camera 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=20260324020132.8683-2-mailingradian@gmail.com \
--to=mailingradian@gmail.com \
--cc=andersson@kernel.org \
--cc=bod@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--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=phone-devel@vger.kernel.org \
--cc=rfoss@kernel.org \
--cc=robert.mader@collabora.com \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tian.shu.qiu@intel.com \
--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