[PATCH] dt-bindings: display: panel: Make DSI panels port optional

[PATCH] dt-bindings: display: panel: Make DSI panels port optional

[Krzysztof Kozlowski]

DSI panels can be placed under DSI bus directly and many Linux DRM
drivers will work fine with it: mipi_dsi_host_register() adds device for
such panel and DRM driver does not use OF graph to configure lanes.  The
affected here Linux panel drivers do not use OF graph, either.

Requiring graph port for such panels is tying the binding to one
specific implementation of Linux DRM drivers, e.g. Qualcomm DRM which
requires the port.  The port is not needed for the hardware to operate
and for some of the Linux drivers, so it should be optional.

Suggested-by: Romain TISSERAND <romain.tisserand@gmail.com>
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

---

Remaining one Ilitek is fixed in:
https://lore.kernel.org/all/20261109160706.2272332-2-romain.tisserand@gmail.com/
---
 .../devicetree/bindings/display/panel/anbernic,td4310.yaml       | 1 -
 Documentation/devicetree/bindings/display/panel/boe,td4320.yaml  | 1 -
 .../devicetree/bindings/display/panel/boe,tv101wum-ll2.yaml      | 1 -
 Documentation/devicetree/bindings/display/panel/ebbg,ft8719.yaml | 1 -
 .../devicetree/bindings/display/panel/elida,kd35t133.yaml        | 1 -
 .../bindings/display/panel/feiyang,fy07024di26a30d.yaml          | 1 -
 .../devicetree/bindings/display/panel/himax,hx83112a.yaml        | 1 -
 .../devicetree/bindings/display/panel/himax,hx83112b.yaml        | 1 -
 .../devicetree/bindings/display/panel/himax,hx8394.yaml          | 1 -
 .../devicetree/bindings/display/panel/ilitek,ili7807s.yaml       | 1 -
 .../devicetree/bindings/display/panel/ilitek,ili9805.yaml        | 1 -
 .../devicetree/bindings/display/panel/ilitek,ili9806e.yaml       | 1 -
 Documentation/devicetree/bindings/display/panel/lxd,m9189a.yaml  | 1 -
 .../devicetree/bindings/display/panel/novatek,nt35532.yaml       | 1 -
 .../devicetree/bindings/display/panel/novatek,nt36672a.yaml      | 1 -
 .../devicetree/bindings/display/panel/novatek,nt36672e.yaml      | 1 -
 .../devicetree/bindings/display/panel/novatek,nt37801.yaml       | 1 -
 .../devicetree/bindings/display/panel/novatek,nt51021.yaml       | 1 -
 .../devicetree/bindings/display/panel/raydium,rm67191.yaml       | 1 -
 .../devicetree/bindings/display/panel/raydium,rm67200.yaml       | 1 -
 .../devicetree/bindings/display/panel/raydium,rm69220.yaml       | 1 -
 .../devicetree/bindings/display/panel/raydium,rm692e5.yaml       | 1 -
 .../devicetree/bindings/display/panel/renesas,r61307.yaml        | 1 -
 .../devicetree/bindings/display/panel/renesas,r69328.yaml        | 1 -
 .../devicetree/bindings/display/panel/ronbo,rb070d30.yaml        | 1 -
 .../devicetree/bindings/display/panel/samsung,ams581vf01.yaml    | 1 -
 .../devicetree/bindings/display/panel/samsung,ams639rq08.yaml    | 1 -
 .../bindings/display/panel/samsung,s6e88a0-ams452ef01.yaml       | 1 -
 .../devicetree/bindings/display/panel/samsung,sofef01-m.yaml     | 1 -
 .../devicetree/bindings/display/panel/sony,td4353-jdi.yaml       | 1 -
 .../bindings/display/panel/sony,tulip-truly-nt35521.yaml         | 1 -
 .../devicetree/bindings/display/panel/startek,kd070fhfid015.yaml | 1 -
 .../devicetree/bindings/display/panel/synaptics,r63353.yaml      | 1 -
 .../devicetree/bindings/display/panel/visionox,g2647fb105.yaml   | 1 -
 .../devicetree/bindings/display/panel/visionox,r66451.yaml       | 1 -
 .../devicetree/bindings/display/panel/visionox,rm69299.yaml      | 1 -
 .../devicetree/bindings/display/panel/visionox,rm692e5.yaml      | 1 -
 .../devicetree/bindings/display/panel/visionox,vtdr6130.yaml     | 1 -
 .../devicetree/bindings/display/panel/xinpeng,xpp055c272.yaml    | 1 -
 39 files changed, 39 deletions(-)

diff --git a/Documentation/devicetree/bindings/display/panel/anbernic,td4310.yaml b/Documentation/devicetree/bindings/display/panel/anbernic,td4310.yaml
index f820dc2f732b..1d6bf6da2ca8 100644
--- a/Documentation/devicetree/bindings/display/panel/anbernic,td4310.yaml
+++ b/Documentation/devicetree/bindings/display/panel/anbernic,td4310.yaml
@@ -31,7 +31,6 @@ properties:
 
 required:
   - compatible
-  - port
   - reg
   - reset-gpios
   - vdd-supply
diff --git a/Documentation/devicetree/bindings/display/panel/boe,td4320.yaml b/Documentation/devicetree/bindings/display/panel/boe,td4320.yaml
index c6bff0ece360..90f0d0bbe91e 100644
--- a/Documentation/devicetree/bindings/display/panel/boe,td4320.yaml
+++ b/Documentation/devicetree/bindings/display/panel/boe,td4320.yaml
@@ -36,7 +36,6 @@ required:
   - compatible
   - reg
   - reset-gpios
-  - port
 
 unevaluatedProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/boe,tv101wum-ll2.yaml b/Documentation/devicetree/bindings/display/panel/boe,tv101wum-ll2.yaml
index dced98e1c69a..45f3205ed952 100644
--- a/Documentation/devicetree/bindings/display/panel/boe,tv101wum-ll2.yaml
+++ b/Documentation/devicetree/bindings/display/panel/boe,tv101wum-ll2.yaml
@@ -33,7 +33,6 @@ required:
   - reset-gpios
   - vsp-supply
   - vsn-supply
-  - port
 
 additionalProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/ebbg,ft8719.yaml b/Documentation/devicetree/bindings/display/panel/ebbg,ft8719.yaml
index 80deedc01c7c..9c6a4d5e9f5b 100644
--- a/Documentation/devicetree/bindings/display/panel/ebbg,ft8719.yaml
+++ b/Documentation/devicetree/bindings/display/panel/ebbg,ft8719.yaml
@@ -41,7 +41,6 @@ required:
   - vddpos-supply
   - vddneg-supply
   - reset-gpios
-  - port
 
 unevaluatedProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/elida,kd35t133.yaml b/Documentation/devicetree/bindings/display/panel/elida,kd35t133.yaml
index f4cb825d1e96..d04ffbba359a 100644
--- a/Documentation/devicetree/bindings/display/panel/elida,kd35t133.yaml
+++ b/Documentation/devicetree/bindings/display/panel/elida,kd35t133.yaml
@@ -32,7 +32,6 @@ required:
   - compatible
   - reg
   - backlight
-  - port
   - iovcc-supply
   - vdd-supply
 
diff --git a/Documentation/devicetree/bindings/display/panel/feiyang,fy07024di26a30d.yaml b/Documentation/devicetree/bindings/display/panel/feiyang,fy07024di26a30d.yaml
index f288fa2390c9..f36e866a1325 100644
--- a/Documentation/devicetree/bindings/display/panel/feiyang,fy07024di26a30d.yaml
+++ b/Documentation/devicetree/bindings/display/panel/feiyang,fy07024di26a30d.yaml
@@ -35,7 +35,6 @@ required:
   - reg
   - avdd-supply
   - dvdd-supply
-  - port
 
 additionalProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/himax,hx83112a.yaml b/Documentation/devicetree/bindings/display/panel/himax,hx83112a.yaml
index 2c60d0cd704e..008a94608c42 100644
--- a/Documentation/devicetree/bindings/display/panel/himax,hx83112a.yaml
+++ b/Documentation/devicetree/bindings/display/panel/himax,hx83112a.yaml
@@ -40,7 +40,6 @@ required:
   - vdd1-supply
   - vsn-supply
   - vsp-supply
-  - port
 
 unevaluatedProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/himax,hx83112b.yaml b/Documentation/devicetree/bindings/display/panel/himax,hx83112b.yaml
index e58bb3d45331..bc1771efb6e9 100644
--- a/Documentation/devicetree/bindings/display/panel/himax,hx83112b.yaml
+++ b/Documentation/devicetree/bindings/display/panel/himax,hx83112b.yaml
@@ -40,7 +40,6 @@ required:
   - iovcc-supply
   - vsn-supply
   - vsp-supply
-  - port
 
 unevaluatedProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/himax,hx8394.yaml b/Documentation/devicetree/bindings/display/panel/himax,hx8394.yaml
index 83c343b02835..41dc3f39f42a 100644
--- a/Documentation/devicetree/bindings/display/panel/himax,hx8394.yaml
+++ b/Documentation/devicetree/bindings/display/panel/himax,hx8394.yaml
@@ -49,7 +49,6 @@ required:
   - compatible
   - reg
   - backlight
-  - port
   - vcc-supply
   - iovcc-supply
 
diff --git a/Documentation/devicetree/bindings/display/panel/ilitek,ili7807s.yaml b/Documentation/devicetree/bindings/display/panel/ilitek,ili7807s.yaml
index ba8c5bbf8ffc..3bace821bc8e 100644
--- a/Documentation/devicetree/bindings/display/panel/ilitek,ili7807s.yaml
+++ b/Documentation/devicetree/bindings/display/panel/ilitek,ili7807s.yaml
@@ -41,7 +41,6 @@ required:
   - vddi-supply
   - avdd-supply
   - avee-supply
-  - port
 
 unevaluatedProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/ilitek,ili9805.yaml b/Documentation/devicetree/bindings/display/panel/ilitek,ili9805.yaml
index ff67129c9466..4bd76a411639 100644
--- a/Documentation/devicetree/bindings/display/panel/ilitek,ili9805.yaml
+++ b/Documentation/devicetree/bindings/display/panel/ilitek,ili9805.yaml
@@ -32,7 +32,6 @@ required:
   - dvdd-supply
   - reg
   - reset-gpios
-  - port
   - backlight
 
 unevaluatedProperties: false
diff --git a/Documentation/devicetree/bindings/display/panel/ilitek,ili9806e.yaml b/Documentation/devicetree/bindings/display/panel/ilitek,ili9806e.yaml
index 2080d9e0ffac..9a2602ddd906 100644
--- a/Documentation/devicetree/bindings/display/panel/ilitek,ili9806e.yaml
+++ b/Documentation/devicetree/bindings/display/panel/ilitek,ili9806e.yaml
@@ -33,7 +33,6 @@ required:
   - vdd-supply
   - reset-gpios
   - backlight
-  - port
 
 if:
   properties:
diff --git a/Documentation/devicetree/bindings/display/panel/lxd,m9189a.yaml b/Documentation/devicetree/bindings/display/panel/lxd,m9189a.yaml
index 226974a4077f..70243c087410 100644
--- a/Documentation/devicetree/bindings/display/panel/lxd,m9189a.yaml
+++ b/Documentation/devicetree/bindings/display/panel/lxd,m9189a.yaml
@@ -35,7 +35,6 @@ required:
   - reset-gpios
   - power-supply
   - backlight
-  - port
 
 additionalProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/novatek,nt35532.yaml b/Documentation/devicetree/bindings/display/panel/novatek,nt35532.yaml
index ff6fdad7febf..a00aabc7f583 100644
--- a/Documentation/devicetree/bindings/display/panel/novatek,nt35532.yaml
+++ b/Documentation/devicetree/bindings/display/panel/novatek,nt35532.yaml
@@ -47,7 +47,6 @@ required:
   - reg
   - reset-gpios
   - vddi-supply
-  - port
 
 additionalProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/novatek,nt36672a.yaml b/Documentation/devicetree/bindings/display/panel/novatek,nt36672a.yaml
index 5d16d8511725..3263e21bf72e 100644
--- a/Documentation/devicetree/bindings/display/panel/novatek,nt36672a.yaml
+++ b/Documentation/devicetree/bindings/display/panel/novatek,nt36672a.yaml
@@ -54,7 +54,6 @@ required:
   - vddpos-supply
   - vddneg-supply
   - reset-gpios
-  - port
 
 unevaluatedProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/novatek,nt36672e.yaml b/Documentation/devicetree/bindings/display/panel/novatek,nt36672e.yaml
index dc4672f3d01d..bb10d62ac2e4 100644
--- a/Documentation/devicetree/bindings/display/panel/novatek,nt36672e.yaml
+++ b/Documentation/devicetree/bindings/display/panel/novatek,nt36672e.yaml
@@ -34,7 +34,6 @@ required:
   - avdd-supply
   - avee-supply
   - reset-gpios
-  - port
 
 additionalProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/novatek,nt37801.yaml b/Documentation/devicetree/bindings/display/panel/novatek,nt37801.yaml
index 1b38c1d0af68..ff7afe5467b6 100644
--- a/Documentation/devicetree/bindings/display/panel/novatek,nt37801.yaml
+++ b/Documentation/devicetree/bindings/display/panel/novatek,nt37801.yaml
@@ -36,7 +36,6 @@ required:
   - vci-supply
   - vdd-supply
   - vddio-supply
-  - port
   - reset-gpios
 
 additionalProperties: false
diff --git a/Documentation/devicetree/bindings/display/panel/novatek,nt51021.yaml b/Documentation/devicetree/bindings/display/panel/novatek,nt51021.yaml
index 7754a8cb1e5c..a50f241e0186 100644
--- a/Documentation/devicetree/bindings/display/panel/novatek,nt51021.yaml
+++ b/Documentation/devicetree/bindings/display/panel/novatek,nt51021.yaml
@@ -54,7 +54,6 @@ required:
   - avdd-supply
   - havdd-supply
   - reset-gpios
-  - port
 
 unevaluatedProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/raydium,rm67191.yaml b/Documentation/devicetree/bindings/display/panel/raydium,rm67191.yaml
index 4825792bf712..511cd2b64fe7 100644
--- a/Documentation/devicetree/bindings/display/panel/raydium,rm67191.yaml
+++ b/Documentation/devicetree/bindings/display/panel/raydium,rm67191.yaml
@@ -47,7 +47,6 @@ required:
   - compatible
   - reg
   - dsi-lanes
-  - port
 
 additionalProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/raydium,rm67200.yaml b/Documentation/devicetree/bindings/display/panel/raydium,rm67200.yaml
index 97b7fbe05c07..cefb5fdee826 100644
--- a/Documentation/devicetree/bindings/display/panel/raydium,rm67200.yaml
+++ b/Documentation/devicetree/bindings/display/panel/raydium,rm67200.yaml
@@ -40,7 +40,6 @@ properties:
 
 required:
   - compatible
-  - port
   - reg
 
 additionalProperties: false
diff --git a/Documentation/devicetree/bindings/display/panel/raydium,rm69220.yaml b/Documentation/devicetree/bindings/display/panel/raydium,rm69220.yaml
index 3c94db88f797..44b416260f20 100644
--- a/Documentation/devicetree/bindings/display/panel/raydium,rm69220.yaml
+++ b/Documentation/devicetree/bindings/display/panel/raydium,rm69220.yaml
@@ -42,7 +42,6 @@ required:
   - vci-supply
   - vddio-supply
   - reset-gpios
-  - port
 
 unevaluatedProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/raydium,rm692e5.yaml b/Documentation/devicetree/bindings/display/panel/raydium,rm692e5.yaml
index 616a5f3ec9fc..91336e17a059 100644
--- a/Documentation/devicetree/bindings/display/panel/raydium,rm692e5.yaml
+++ b/Documentation/devicetree/bindings/display/panel/raydium,rm692e5.yaml
@@ -41,7 +41,6 @@ required:
   - dvdd-supply
   - vci-supply
   - vddio-supply
-  - port
 
 unevaluatedProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/renesas,r61307.yaml b/Documentation/devicetree/bindings/display/panel/renesas,r61307.yaml
index 3d7761717b74..aff691fdb771 100644
--- a/Documentation/devicetree/bindings/display/panel/renesas,r61307.yaml
+++ b/Documentation/devicetree/bindings/display/panel/renesas,r61307.yaml
@@ -55,7 +55,6 @@ properties:
 
 required:
   - compatible
-  - port
   - backlight
 
 additionalProperties: false
diff --git a/Documentation/devicetree/bindings/display/panel/renesas,r69328.yaml b/Documentation/devicetree/bindings/display/panel/renesas,r69328.yaml
index 740185f778a1..c28b671d8721 100644
--- a/Documentation/devicetree/bindings/display/panel/renesas,r69328.yaml
+++ b/Documentation/devicetree/bindings/display/panel/renesas,r69328.yaml
@@ -38,7 +38,6 @@ properties:
 
 required:
   - compatible
-  - port
   - backlight
 
 additionalProperties: false
diff --git a/Documentation/devicetree/bindings/display/panel/ronbo,rb070d30.yaml b/Documentation/devicetree/bindings/display/panel/ronbo,rb070d30.yaml
index 694037301583..b17b7ce2b29e 100644
--- a/Documentation/devicetree/bindings/display/panel/ronbo,rb070d30.yaml
+++ b/Documentation/devicetree/bindings/display/panel/ronbo,rb070d30.yaml
@@ -42,6 +42,5 @@ required:
   - shlr-gpios
   - updn-gpios
   - vcc-lcd-supply
-  - port
 
 unevaluatedProperties: false
diff --git a/Documentation/devicetree/bindings/display/panel/samsung,ams581vf01.yaml b/Documentation/devicetree/bindings/display/panel/samsung,ams581vf01.yaml
index 70dff9c0ef2b..5e1fb1edb3e0 100644
--- a/Documentation/devicetree/bindings/display/panel/samsung,ams581vf01.yaml
+++ b/Documentation/devicetree/bindings/display/panel/samsung,ams581vf01.yaml
@@ -45,7 +45,6 @@ required:
   - vsn-supply
   - vsp-supply
   - reset-gpios
-  - port
 
 additionalProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/samsung,ams639rq08.yaml b/Documentation/devicetree/bindings/display/panel/samsung,ams639rq08.yaml
index f5b6ecb96f99..3a68324a2b69 100644
--- a/Documentation/devicetree/bindings/display/panel/samsung,ams639rq08.yaml
+++ b/Documentation/devicetree/bindings/display/panel/samsung,ams639rq08.yaml
@@ -46,7 +46,6 @@ required:
   - vsn-supply
   - vsp-supply
   - reset-gpios
-  - port
 
 additionalProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/samsung,s6e88a0-ams452ef01.yaml b/Documentation/devicetree/bindings/display/panel/samsung,s6e88a0-ams452ef01.yaml
index 42634fc3b5b2..25eadff02816 100644
--- a/Documentation/devicetree/bindings/display/panel/samsung,s6e88a0-ams452ef01.yaml
+++ b/Documentation/devicetree/bindings/display/panel/samsung,s6e88a0-ams452ef01.yaml
@@ -29,7 +29,6 @@ properties:
 required:
   - compatible
   - reg
-  - port
   - vdd3-supply
   - vci-supply
   - reset-gpios
diff --git a/Documentation/devicetree/bindings/display/panel/samsung,sofef01-m.yaml b/Documentation/devicetree/bindings/display/panel/samsung,sofef01-m.yaml
index bccc667aa072..c0a44e69b37e 100644
--- a/Documentation/devicetree/bindings/display/panel/samsung,sofef01-m.yaml
+++ b/Documentation/devicetree/bindings/display/panel/samsung,sofef01-m.yaml
@@ -47,7 +47,6 @@ properties:
 
 required:
   - compatible
-  - port
   - reg
   - reset-gpios
   - vddio-supply
diff --git a/Documentation/devicetree/bindings/display/panel/sony,td4353-jdi.yaml b/Documentation/devicetree/bindings/display/panel/sony,td4353-jdi.yaml
index 032a989184ff..ccfc0513eb4a 100644
--- a/Documentation/devicetree/bindings/display/panel/sony,td4353-jdi.yaml
+++ b/Documentation/devicetree/bindings/display/panel/sony,td4353-jdi.yaml
@@ -52,7 +52,6 @@ required:
   - vsn-supply
   - panel-reset-gpios
   - touch-reset-gpios
-  - port
 
 additionalProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/sony,tulip-truly-nt35521.yaml b/Documentation/devicetree/bindings/display/panel/sony,tulip-truly-nt35521.yaml
index 85c5dee65383..85977dfe8b72 100644
--- a/Documentation/devicetree/bindings/display/panel/sony,tulip-truly-nt35521.yaml
+++ b/Documentation/devicetree/bindings/display/panel/sony,tulip-truly-nt35521.yaml
@@ -41,7 +41,6 @@ required:
   - negative5-supply
   - reset-gpios
   - enable-gpios
-  - port
 
 additionalProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/startek,kd070fhfid015.yaml b/Documentation/devicetree/bindings/display/panel/startek,kd070fhfid015.yaml
index 7fd9364fa385..4c7677f6b154 100644
--- a/Documentation/devicetree/bindings/display/panel/startek,kd070fhfid015.yaml
+++ b/Documentation/devicetree/bindings/display/panel/startek,kd070fhfid015.yaml
@@ -34,7 +34,6 @@ required:
   - iovcc-supply
   - reg
   - reset-gpios
-  - port
   - power-supply
 
 additionalProperties: false
diff --git a/Documentation/devicetree/bindings/display/panel/synaptics,r63353.yaml b/Documentation/devicetree/bindings/display/panel/synaptics,r63353.yaml
index 2fd6e0ec3682..6a0c7518531a 100644
--- a/Documentation/devicetree/bindings/display/panel/synaptics,r63353.yaml
+++ b/Documentation/devicetree/bindings/display/panel/synaptics,r63353.yaml
@@ -31,7 +31,6 @@ required:
   - avdd-supply
   - dvdd-supply
   - reset-gpios
-  - port
   - backlight
 
 unevaluatedProperties: false
diff --git a/Documentation/devicetree/bindings/display/panel/visionox,g2647fb105.yaml b/Documentation/devicetree/bindings/display/panel/visionox,g2647fb105.yaml
index 49dcd9b8f670..ea79ea070adc 100644
--- a/Documentation/devicetree/bindings/display/panel/visionox,g2647fb105.yaml
+++ b/Documentation/devicetree/bindings/display/panel/visionox,g2647fb105.yaml
@@ -45,7 +45,6 @@ required:
   - vsn-supply
   - vsp-supply
   - reset-gpios
-  - port
 
 additionalProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/visionox,r66451.yaml b/Documentation/devicetree/bindings/display/panel/visionox,r66451.yaml
index 49ef45c03593..281333b781ba 100644
--- a/Documentation/devicetree/bindings/display/panel/visionox,r66451.yaml
+++ b/Documentation/devicetree/bindings/display/panel/visionox,r66451.yaml
@@ -31,7 +31,6 @@ required:
   - vddio-supply
   - vdd-supply
   - reset-gpios
-  - port
 
 additionalProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/visionox,rm69299.yaml b/Documentation/devicetree/bindings/display/panel/visionox,rm69299.yaml
index f61a528c0413..bcde74217e1b 100644
--- a/Documentation/devicetree/bindings/display/panel/visionox,rm69299.yaml
+++ b/Documentation/devicetree/bindings/display/panel/visionox,rm69299.yaml
@@ -42,7 +42,6 @@ required:
   - vdda-supply
   - vdd3p3-supply
   - reset-gpios
-  - port
 
 additionalProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/visionox,rm692e5.yaml b/Documentation/devicetree/bindings/display/panel/visionox,rm692e5.yaml
index d4b4672815fe..ec393d15423f 100644
--- a/Documentation/devicetree/bindings/display/panel/visionox,rm692e5.yaml
+++ b/Documentation/devicetree/bindings/display/panel/visionox,rm692e5.yaml
@@ -44,7 +44,6 @@ required:
   - reset-gpios
   - vdd-supply
   - vddio-supply
-  - port
 
 additionalProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/visionox,vtdr6130.yaml b/Documentation/devicetree/bindings/display/panel/visionox,vtdr6130.yaml
index 682f30dc9ee4..979c5b95fac9 100644
--- a/Documentation/devicetree/bindings/display/panel/visionox,vtdr6130.yaml
+++ b/Documentation/devicetree/bindings/display/panel/visionox,vtdr6130.yaml
@@ -37,7 +37,6 @@ required:
   - vddio-supply
   - vci-supply
   - reset-gpios
-  - port
 
 additionalProperties: false
 
diff --git a/Documentation/devicetree/bindings/display/panel/xinpeng,xpp055c272.yaml b/Documentation/devicetree/bindings/display/panel/xinpeng,xpp055c272.yaml
index 9c9743a23500..13ff075bd2a6 100644
--- a/Documentation/devicetree/bindings/display/panel/xinpeng,xpp055c272.yaml
+++ b/Documentation/devicetree/bindings/display/panel/xinpeng,xpp055c272.yaml
@@ -31,7 +31,6 @@ required:
   - compatible
   - reg
   - backlight
-  - port
   - iovcc-supply
   - vci-supply
 
-- 
2.53.0

Re: [PATCH] dt-bindings: display: panel: Make DSI panels port optional

[Maxime Ripard]

[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]

On Wed, Nov 11, 2026 at 12:03:39PM +0100, Krzysztof Kozlowski wrote:
> DSI panels can be placed under DSI bus directly and many Linux DRM
> drivers will work fine with it: mipi_dsi_host_register() adds device for
> such panel and DRM driver does not use OF graph to configure lanes.

That's not true. We do use the endpoints to configure the lanes through
the data-lanes property. See drm_of_get_data_lanes*

> The affected here Linux panel drivers do not use OF graph, either.
> 
> Requiring graph port for such panels is tying the binding to one
> specific implementation of Linux DRM drivers, e.g. Qualcomm DRM which
> requires the port.  The port is not needed for the hardware to operate
> and for some of the Linux drivers, so it should be optional.
> 
> Suggested-by: Romain TISSERAND <romain.tisserand@gmail.com>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

DSI busses can handle multiple devices, and multiple data types. If we
were to drop the port node, how does the upstream video device know
which device it should send its video output to?

Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]

Re: [PATCH] dt-bindings: display: panel: Make DSI panels port optional

[Krzysztof Kozlowski]

On 11/11/2026 12:13, Maxime Ripard wrote:
> On Wed, Nov 11, 2026 at 12:03:39PM +0100, Krzysztof Kozlowski wrote:
>> DSI panels can be placed under DSI bus directly and many Linux DRM
>> drivers will work fine with it: mipi_dsi_host_register() adds device for
>> such panel and DRM driver does not use OF graph to configure lanes.
> 
> That's not true. We do use the endpoints to configure the lanes through
> the data-lanes property. See drm_of_get_data_lanes*

Some drivers use endpoints, some not. As discussed on other thread,
there are more than which do not.

> 
>> The affected here Linux panel drivers do not use OF graph, either.
>>
>> Requiring graph port for such panels is tying the binding to one
>> specific implementation of Linux DRM drivers, e.g. Qualcomm DRM which
>> requires the port.  The port is not needed for the hardware to operate
>> and for some of the Linux drivers, so it should be optional.
>>
>> Suggested-by: Romain TISSERAND <romain.tisserand@gmail.com>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> 
> DSI busses can handle multiple devices, and multiple data types. If we
> were to drop the port node, how does the upstream video device know
> which device it should send its video output to?
> 

We do not drop the port node, who suggested that?

You do get, that we are not talking about the DSI host, but the panel?


Best regards,
Krzysztof

Re: [PATCH] dt-bindings: display: panel: Make DSI panels port optional

[Krzysztof Kozlowski]

On 11/11/2026 13:30, Krzysztof Kozlowski wrote:
> On 11/11/2026 12:13, Maxime Ripard wrote:
>> On Wed, Nov 11, 2026 at 12:03:39PM +0100, Krzysztof Kozlowski wrote:
>>> DSI panels can be placed under DSI bus directly and many Linux DRM
>>> drivers will work fine with it: mipi_dsi_host_register() adds device for
>>> such panel and DRM driver does not use OF graph to configure lanes.
>>
>> That's not true. We do use the endpoints to configure the lanes through
>> the data-lanes property. See drm_of_get_data_lanes*
> 
> Some drivers use endpoints, some not. As discussed on other thread,
> there are more than which do not.

"there are more than one which do not."

> 
>>
>>> The affected here Linux panel drivers do not use OF graph, either.
>>>
>>> Requiring graph port for such panels is tying the binding to one
>>> specific implementation of Linux DRM drivers, e.g. Qualcomm DRM which
>>> requires the port.  The port is not needed for the hardware to operate
>>> and for some of the Linux drivers, so it should be optional.
>>>
>>> Suggested-by: Romain TISSERAND <romain.tisserand@gmail.com>
>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>>
>> DSI busses can handle multiple devices, and multiple data types. If we
>> were to drop the port node, how does the upstream video device know
>> which device it should send its video output to?
>>
> 
> We do not drop the port node, who suggested that?
> 
> You do get, that we are not talking about the DSI host, but the panel?

Best regards,
Krzysztof

Re: [PATCH] dt-bindings: display: panel: Make DSI panels port optional

[Dmitry Baryshkov]

On Wed, Nov 11, 2026 at 01:31:39PM +0100, Krzysztof Kozlowski wrote:
> On 11/11/2026 13:30, Krzysztof Kozlowski wrote:
> > On 11/11/2026 12:13, Maxime Ripard wrote:
> >> On Wed, Nov 11, 2026 at 12:03:39PM +0100, Krzysztof Kozlowski wrote:
> >>> DSI panels can be placed under DSI bus directly and many Linux DRM
> >>> drivers will work fine with it: mipi_dsi_host_register() adds device for
> >>> such panel and DRM driver does not use OF graph to configure lanes.
> >>
> >> That's not true. We do use the endpoints to configure the lanes through
> >> the data-lanes property. See drm_of_get_data_lanes*
> > 
> > Some drivers use endpoints, some not. As discussed on other thread,
> > there are more than which do not.
> 
> "there are more than one which do not."

Which means that those should be fixed. We have legacy cases where the
drivers assumed that, but we should not target legacy.

> 
> > 
> >>
> >>> The affected here Linux panel drivers do not use OF graph, either.
> >>>
> >>> Requiring graph port for such panels is tying the binding to one
> >>> specific implementation of Linux DRM drivers, e.g. Qualcomm DRM which
> >>> requires the port.  The port is not needed for the hardware to operate
> >>> and for some of the Linux drivers, so it should be optional.
> >>>
> >>> Suggested-by: Romain TISSERAND <romain.tisserand@gmail.com>
> >>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> >>
> >> DSI busses can handle multiple devices, and multiple data types. If we
> >> were to drop the port node, how does the upstream video device know
> >> which device it should send its video output to?
> >>
> > 
> > We do not drop the port node, who suggested that?
> > 
> > You do get, that we are not talking about the DSI host, but the panel?

The panel might be driven by the host directly or there can be other
chips on the bus (someboby has been asking about the retimer or
something else sitting on the DSI bus between the host and the panel).

-- 
With best wishes
Dmitry

Re: [PATCH] dt-bindings: display: panel: Make DSI panels port optional

[Krzysztof Kozlowski]

On 11/11/2026 13:37, Dmitry Baryshkov wrote:
> On Wed, Nov 11, 2026 at 01:31:39PM +0100, Krzysztof Kozlowski wrote:
>> On 11/11/2026 13:30, Krzysztof Kozlowski wrote:
>>> On 11/11/2026 12:13, Maxime Ripard wrote:
>>>> On Wed, Nov 11, 2026 at 12:03:39PM +0100, Krzysztof Kozlowski wrote:
>>>>> DSI panels can be placed under DSI bus directly and many Linux DRM
>>>>> drivers will work fine with it: mipi_dsi_host_register() adds device for
>>>>> such panel and DRM driver does not use OF graph to configure lanes.
>>>>
>>>> That's not true. We do use the endpoints to configure the lanes through
>>>> the data-lanes property. See drm_of_get_data_lanes*
>>>
>>> Some drivers use endpoints, some not. As discussed on other thread,
>>> there are more than which do not.
>>
>> "there are more than one which do not."
> 
> Which means that those should be fixed. We have legacy cases where the
> drivers assumed that, but we should not target legacy.

These legacy drivers work fine for 10 or 15 years, like Exynos.

You can improve them, for sure, but if no one does that then requiring a
graph is a mistake there, from the panel point of view.

...

>>>> DSI busses can handle multiple devices, and multiple data types. If we
>>>> were to drop the port node, how does the upstream video device know
>>>> which device it should send its video output to?
>>>>
>>>
>>> We do not drop the port node, who suggested that?
>>>
>>> You do get, that we are not talking about the DSI host, but the panel?
> 
> The panel might be driven by the host directly or there can be other
> chips on the bus (someboby has been asking about the retimer or
> something else sitting on the DSI bus between the host and the panel).

Sure, does not change that panel DOES NOT require the graph node.
Neither current Linux drivers, except some.

Best regards,
Krzysztof

Re: [PATCH] dt-bindings: display: panel: Make DSI panels port optional

[Maxime Ripard]

[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]

On Wed, Nov 11, 2026 at 01:44:23PM +0100, Krzysztof Kozlowski wrote:
> On 11/11/2026 13:37, Dmitry Baryshkov wrote:
> > On Wed, Nov 11, 2026 at 01:31:39PM +0100, Krzysztof Kozlowski wrote:
> >> On 11/11/2026 13:30, Krzysztof Kozlowski wrote:
> >>> On 11/11/2026 12:13, Maxime Ripard wrote:
> >>>> On Wed, Nov 11, 2026 at 12:03:39PM +0100, Krzysztof Kozlowski wrote:
> >>>>> DSI panels can be placed under DSI bus directly and many Linux DRM
> >>>>> drivers will work fine with it: mipi_dsi_host_register() adds device for
> >>>>> such panel and DRM driver does not use OF graph to configure lanes.
> >>>>
> >>>> That's not true. We do use the endpoints to configure the lanes through
> >>>> the data-lanes property. See drm_of_get_data_lanes*
> >>>
> >>> Some drivers use endpoints, some not. As discussed on other thread,
> >>> there are more than which do not.
> >>
> >> "there are more than one which do not."
> > 
> > Which means that those should be fixed. We have legacy cases where the
> > drivers assumed that, but we should not target legacy.
> 
> These legacy drivers work fine for 10 or 15 years, like Exynos.
> 
> You can improve them, for sure, but if no one does that then requiring a
> graph is a mistake there, from the panel point of view.

At the very least the commit log needs some work then, because the
situation you describe in it is simply wrong, and quite different to the
situation you then described.

Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]

Re: [PATCH] dt-bindings: display: panel: Make DSI panels port optional

[Krzysztof Kozlowski]

On 11/11/2026 14:52, Maxime Ripard wrote:
> On Wed, Nov 11, 2026 at 01:44:23PM +0100, Krzysztof Kozlowski wrote:
>> On 11/11/2026 13:37, Dmitry Baryshkov wrote:
>>> On Wed, Nov 11, 2026 at 01:31:39PM +0100, Krzysztof Kozlowski wrote:
>>>> On 11/11/2026 13:30, Krzysztof Kozlowski wrote:
>>>>> On 11/11/2026 12:13, Maxime Ripard wrote:
>>>>>> On Wed, Nov 11, 2026 at 12:03:39PM +0100, Krzysztof Kozlowski wrote:
>>>>>>> DSI panels can be placed under DSI bus directly and many Linux DRM
>>>>>>> drivers will work fine with it: mipi_dsi_host_register() adds device for
>>>>>>> such panel and DRM driver does not use OF graph to configure lanes.
>>>>>>
>>>>>> That's not true. We do use the endpoints to configure the lanes through
>>>>>> the data-lanes property. See drm_of_get_data_lanes*
>>>>>
>>>>> Some drivers use endpoints, some not. As discussed on other thread,
>>>>> there are more than which do not.
>>>>
>>>> "there are more than one which do not."
>>>
>>> Which means that those should be fixed. We have legacy cases where the
>>> drivers assumed that, but we should not target legacy.
>>
>> These legacy drivers work fine for 10 or 15 years, like Exynos.
>>
>> You can improve them, for sure, but if no one does that then requiring a
>> graph is a mistake there, from the panel point of view.
> 
> At the very least the commit log needs some work then, because the
> situation you describe in it is simply wrong, and quite different to the
> situation you then described.


Commit msg said:
"many Linux DRM drivers will work fine with it"

So many->some? Is this the only problem? What else is not described in
commit msg?


Best regards,
Krzysztof

Re: [PATCH] dt-bindings: display: panel: Make DSI panels port optional

[Dmitry Baryshkov]

On Wed, Nov 11, 2026 at 02:54:54PM +0100, Krzysztof Kozlowski wrote:
> On 11/11/2026 14:52, Maxime Ripard wrote:
> > On Wed, Nov 11, 2026 at 01:44:23PM +0100, Krzysztof Kozlowski wrote:
> >> On 11/11/2026 13:37, Dmitry Baryshkov wrote:
> >>> On Wed, Nov 11, 2026 at 01:31:39PM +0100, Krzysztof Kozlowski wrote:
> >>>> On 11/11/2026 13:30, Krzysztof Kozlowski wrote:
> >>>>> On 11/11/2026 12:13, Maxime Ripard wrote:
> >>>>>> On Wed, Nov 11, 2026 at 12:03:39PM +0100, Krzysztof Kozlowski wrote:
> >>>>>>> DSI panels can be placed under DSI bus directly and many Linux DRM
> >>>>>>> drivers will work fine with it: mipi_dsi_host_register() adds device for
> >>>>>>> such panel and DRM driver does not use OF graph to configure lanes.
> >>>>>>
> >>>>>> That's not true. We do use the endpoints to configure the lanes through
> >>>>>> the data-lanes property. See drm_of_get_data_lanes*
> >>>>>
> >>>>> Some drivers use endpoints, some not. As discussed on other thread,
> >>>>> there are more than which do not.
> >>>>
> >>>> "there are more than one which do not."
> >>>
> >>> Which means that those should be fixed. We have legacy cases where the
> >>> drivers assumed that, but we should not target legacy.
> >>
> >> These legacy drivers work fine for 10 or 15 years, like Exynos.
> >>
> >> You can improve them, for sure, but if no one does that then requiring a
> >> graph is a mistake there, from the panel point of view.
> > 
> > At the very least the commit log needs some work then, because the
> > situation you describe in it is simply wrong, and quite different to the
> > situation you then described.
> 
> 
> Commit msg said:
> "many Linux DRM drivers will work fine with it"
> 
> So many->some? Is this the only problem? What else is not described in
> commit msg?

The commit message points out that a minority of drivers use and require
the port, while majority of the drivers don't. I think up to now only
the Exynos and sunXi were mentioned. From my point of view, it would be
better to change corresponding DSI host bindings to allow port bindings
and then define the OF graph connecting DSI host to DSI panel (which
might be done gradually, etc.) even if the OF graph is not used nowadays
by those drivers instead of providing a false signal that it's okay to
have DSI links without OF graph connection. It's not future-proof and
not okay, especially for the new designs.

-- 
With best wishes
Dmitry

Re: [PATCH] dt-bindings: display: panel: Make DSI panels port optional

[Krzysztof Kozlowski]

On 11/11/2026 18:55, Dmitry Baryshkov wrote:
> On Wed, Nov 11, 2026 at 02:54:54PM +0100, Krzysztof Kozlowski wrote:
>>
>> Commit msg said:
>> "many Linux DRM drivers will work fine with it"
>>
>> So many->some? Is this the only problem? What else is not described in
>> commit msg?
> 
> The commit message points out that a minority of drivers use and require
> the port, while majority of the drivers don't. I think up to now only

Ack

> the Exynos and sunXi were mentioned. From my point of view, it would be
> better to change corresponding DSI host bindings to allow port bindings
> and then define the OF graph connecting DSI host to DSI panel (which
> might be done gradually, etc.) even if the OF graph is not used nowadays
> by those drivers instead of providing a false signal that it's okay to
> have DSI links without OF graph connection. It's not future-proof and
> not okay, especially for the new designs.

Around 33% of DSI panels bindings do not require port, so to fulfill
above their bindings should be changed and ABI broken by requiring now a
panel.

Even though neither the panel hardware nor the panel driver needs the port.

The requirement of the port is on DSI host drivers, thus it should be
required there, just like I did for MSM bindings today.

Best regards,
Krzysztof

Re: [PATCH] dt-bindings: display: panel: Make DSI panels port optional

[Icenowy Zheng]

在 2026-11-11三的 12:13 +0100，Maxime Ripard写道：
> On Wed, Nov 11, 2026 at 12:03:39PM +0100, Krzysztof Kozlowski wrote:
> > DSI panels can be placed under DSI bus directly and many Linux DRM
> > drivers will work fine with it: mipi_dsi_host_register() adds
> > device for
> > such panel and DRM driver does not use OF graph to configure lanes.
> 
> That's not true. We do use the endpoints to configure the lanes
> through
> the data-lanes property. See drm_of_get_data_lanes*
> 
> > The affected here Linux panel drivers do not use OF graph, either.
> > 
> > Requiring graph port for such panels is tying the binding to one
> > specific implementation of Linux DRM drivers, e.g. Qualcomm DRM
> > which
> > requires the port.  The port is not needed for the hardware to
> > operate
> > and for some of the Linux drivers, so it should be optional.
> > 
> > Suggested-by: Romain TISSERAND <romain.tisserand@gmail.com>
> > Signed-off-by: Krzysztof Kozlowski
> > <krzysztof.kozlowski@oss.qualcomm.com>
> 
> DSI busses can handle multiple devices, and multiple data types. If
> we
> were to drop the port node, how does the upstream video device know
> which device it should send its video output to?

BTW I checked sun6i-mipi-dsi (which is the driver cared in the other
thread), and it assumes the first DSI device attached is the panel.

Maybe this is some kind of overfit, assuming a 1-to-1 connection?

(And I wonder if anyone attached a bridge instead of a panel to a sunXi
device.)

Thanks,
Icenowy

> 
> Maxime

Re: [PATCH] dt-bindings: display: panel: Make DSI panels port optional

[Svyatoslav Ryhel]

ср, 11 лист. 2026 р. о 13:03 Krzysztof Kozlowski
<krzysztof.kozlowski@oss.qualcomm.com> пише:
>
> DSI panels can be placed under DSI bus directly and many Linux DRM
> drivers will work fine with it: mipi_dsi_host_register() adds device for
> such panel and DRM driver does not use OF graph to configure lanes.  The
> affected here Linux panel drivers do not use OF graph, either.
>
> Requiring graph port for such panels is tying the binding to one
> specific implementation of Linux DRM drivers, e.g. Qualcomm DRM which
> requires the port.  The port is not needed for the hardware to operate
> and for some of the Linux drivers, so it should be optional.
>
> Suggested-by: Romain TISSERAND <romain.tisserand@gmail.com>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>
> ---
>
> Remaining one Ilitek is fixed in:
> https://lore.kernel.org/all/20261109160706.2272332-2-romain.tisserand@gmail.com/
> ---
>  .../devicetree/bindings/display/panel/anbernic,td4310.yaml       | 1 -
>  Documentation/devicetree/bindings/display/panel/boe,td4320.yaml  | 1 -
>  .../devicetree/bindings/display/panel/boe,tv101wum-ll2.yaml      | 1 -
>  Documentation/devicetree/bindings/display/panel/ebbg,ft8719.yaml | 1 -
>  .../devicetree/bindings/display/panel/elida,kd35t133.yaml        | 1 -
>  .../bindings/display/panel/feiyang,fy07024di26a30d.yaml          | 1 -
>  .../devicetree/bindings/display/panel/himax,hx83112a.yaml        | 1 -
>  .../devicetree/bindings/display/panel/himax,hx83112b.yaml        | 1 -
>  .../devicetree/bindings/display/panel/himax,hx8394.yaml          | 1 -
>  .../devicetree/bindings/display/panel/ilitek,ili7807s.yaml       | 1 -
>  .../devicetree/bindings/display/panel/ilitek,ili9805.yaml        | 1 -
>  .../devicetree/bindings/display/panel/ilitek,ili9806e.yaml       | 1 -
>  Documentation/devicetree/bindings/display/panel/lxd,m9189a.yaml  | 1 -
>  .../devicetree/bindings/display/panel/novatek,nt35532.yaml       | 1 -
>  .../devicetree/bindings/display/panel/novatek,nt36672a.yaml      | 1 -
>  .../devicetree/bindings/display/panel/novatek,nt36672e.yaml      | 1 -
>  .../devicetree/bindings/display/panel/novatek,nt37801.yaml       | 1 -
>  .../devicetree/bindings/display/panel/novatek,nt51021.yaml       | 1 -
>  .../devicetree/bindings/display/panel/raydium,rm67191.yaml       | 1 -
>  .../devicetree/bindings/display/panel/raydium,rm67200.yaml       | 1 -
>  .../devicetree/bindings/display/panel/raydium,rm69220.yaml       | 1 -
>  .../devicetree/bindings/display/panel/raydium,rm692e5.yaml       | 1 -
>  .../devicetree/bindings/display/panel/renesas,r61307.yaml        | 1 -
>  .../devicetree/bindings/display/panel/renesas,r69328.yaml        | 1 -
>  .../devicetree/bindings/display/panel/ronbo,rb070d30.yaml        | 1 -
>  .../devicetree/bindings/display/panel/samsung,ams581vf01.yaml    | 1 -
>  .../devicetree/bindings/display/panel/samsung,ams639rq08.yaml    | 1 -
>  .../bindings/display/panel/samsung,s6e88a0-ams452ef01.yaml       | 1 -
>  .../devicetree/bindings/display/panel/samsung,sofef01-m.yaml     | 1 -
>  .../devicetree/bindings/display/panel/sony,td4353-jdi.yaml       | 1 -
>  .../bindings/display/panel/sony,tulip-truly-nt35521.yaml         | 1 -
>  .../devicetree/bindings/display/panel/startek,kd070fhfid015.yaml | 1 -
>  .../devicetree/bindings/display/panel/synaptics,r63353.yaml      | 1 -
>  .../devicetree/bindings/display/panel/visionox,g2647fb105.yaml   | 1 -
>  .../devicetree/bindings/display/panel/visionox,r66451.yaml       | 1 -
>  .../devicetree/bindings/display/panel/visionox,rm69299.yaml      | 1 -
>  .../devicetree/bindings/display/panel/visionox,rm692e5.yaml      | 1 -
>  .../devicetree/bindings/display/panel/visionox,vtdr6130.yaml     | 1 -
>  .../devicetree/bindings/display/panel/xinpeng,xpp055c272.yaml    | 1 -
>  39 files changed, 39 deletions(-)
>

Thanks!

Reviewed-by: Svyatoslav Ryhel <clamor95@gmail.com> # for renesas
r61307 and r69328