On 10/02/2026 02:02, Richard Acayan wrote:
The clock-lanes property has no effect on the hardware configuration, as
of 336136e197e2 ("media: dt-bindings: media: camss: Remove clock-lane
property"). Remove the clock-lanes property.
Suggested-by: Vladimir Zapolskiy <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Richard Acayan <[email protected]>
---
.../bindings/media/qcom,sdm670-camss.yaml | 13 -------------
1 file changed, 13 deletions(-)
diff --git a/Documentation/devicetree/bindings/media/qcom,sdm670-camss.yaml
b/Documentation/devicetree/bindings/media/qcom,sdm670-camss.yaml
index 35c40fe22376..78b9e03da06b 100644
--- a/Documentation/devicetree/bindings/media/qcom,sdm670-camss.yaml
+++ b/Documentation/devicetree/bindings/media/qcom,sdm670-camss.yaml
@@ -116,15 +116,11 @@ properties:
unevaluatedProperties: false
properties:
- clock-lanes:
- maxItems: 1
-
data-lanes:
minItems: 1
maxItems: 4
required:
- - clock-lanes
- data-lanes
port@1:
@@ -139,15 +135,11 @@ properties:
unevaluatedProperties: false
properties:
- clock-lanes:
- maxItems: 1
-
data-lanes:
minItems: 1
maxItems: 4
required:
- - clock-lanes
- data-lanes
port@2:
@@ -162,15 +154,11 @@ properties:
unevaluatedProperties: false
properties:
- clock-lanes:
- maxItems: 1
-
data-lanes:
minItems: 1
maxItems: 4
required:
- - clock-lanes
- data-lanes
required:
@@ -308,7 +296,6 @@ examples:
reg = <0>;
csiphy_ep0: endpoint {
- clock-lanes = <7>;
data-lanes = <0 1 2 3>;
remote-endpoint = <&front_sensor_ep>;
};
I think the ask was to have clock-lanes in the board dts rather than
dropping the clock-lanes from the yaml.
We want to keep clock-lanes in general as some SoCs support changing the
lane assignment.
---
bod
