Document the optional port node, which is required for correctly modeling
a dual-mode panel.
Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
---
.../bindings/display/tegra/nvidia,tegra20-dsi.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml
index 59e1dc0813e7..0f4837648d17 100644
--- a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml
+++ b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml
@@ -83,6 +83,12 @@ properties:
gang up with in order to support up to 8 data lanes
$ref: /schemas/types.yaml#/definitions/phandle
+ port:
+ description: specifies the connection port for the dual-mode panel
+ and is required only when the panel is operating in dual-mode
+ configuration.
+ $ref: /schemas/graph.yaml#/properties/port
+
allOf:
- $ref: ../dsi-controller.yaml#
- if:
--
2.51.0
On Thu, Mar 05, 2026 at 06:10:34PM +0200, Svyatoslav Ryhel wrote: > Document the optional port node, which is required for correctly modeling > a dual-mode panel. Dual mode as in command mode and sync mode? Or do you mean dual link like panel-common-dual.yaml defines? > > Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com> > --- > .../bindings/display/tegra/nvidia,tegra20-dsi.yaml | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml > index 59e1dc0813e7..0f4837648d17 100644 > --- a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml > +++ b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml > @@ -83,6 +83,12 @@ properties: > gang up with in order to support up to 8 data lanes > $ref: /schemas/types.yaml#/definitions/phandle > > + port: > + description: specifies the connection port for the dual-mode panel > + and is required only when the panel is operating in dual-mode > + configuration. > + $ref: /schemas/graph.yaml#/properties/port > + > allOf: > - $ref: ../dsi-controller.yaml# > - if: > -- > 2.51.0 >
чт, 12 бер. 2026 р. о 16:57 Rob Herring <robh@kernel.org> пише: > > On Thu, Mar 05, 2026 at 06:10:34PM +0200, Svyatoslav Ryhel wrote: > > Document the optional port node, which is required for correctly modeling > > a dual-mode panel. > > Dual mode as in command mode and sync mode? Or do you mean dual link > like panel-common-dual.yaml defines? > Dual link like in panel-common-dual but that panel-common-dual should not be suitable for DSI controller/host. Tegra DSI expects panel to be defined as in dsi-controller.yaml while this port node is solely to cover dual-link mode panels. Command mode and video/sync mode usually refer to how driver should work and usually are not mentioned in the schema. > > > > Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com> > > --- > > .../bindings/display/tegra/nvidia,tegra20-dsi.yaml | 6 ++++++ > > 1 file changed, 6 insertions(+) > > > > diff --git a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml > > index 59e1dc0813e7..0f4837648d17 100644 > > --- a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml > > +++ b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml > > @@ -83,6 +83,12 @@ properties: > > gang up with in order to support up to 8 data lanes > > $ref: /schemas/types.yaml#/definitions/phandle > > > > + port: > > + description: specifies the connection port for the dual-mode panel > > + and is required only when the panel is operating in dual-mode > > + configuration. > > + $ref: /schemas/graph.yaml#/properties/port > > + > > allOf: > > - $ref: ../dsi-controller.yaml# > > - if: > > -- > > 2.51.0 > >
© 2016 - 2026 Red Hat, Inc.