Display Device Tree#

This topic applies only to Linux builds running on Thor and C-X1 platforms.

Display element in 7.2.5.0 supports the following device tree.

Thor platforms can support at most 8 heads.

The HEADS are assigned to respective displays. The number of physical displays corresponds to the number of dpy nodes in the Device Tree (DT). The connectors available on the device are represented by connector nodes, with the dpy node managing the head-to-connector association.

tegra264-p3960-disp-config.dtsi

display@8808c00000 {
   dpys {
         dpy-0 {
            hw-head-id = <0>;
            timing-id = <0>;
            connector-id = <0>;
         };
         dpy-1 {
            hw-head-id = <1>;
            timing-id = <0>;
            connector-id = <1>;
         };
         dpy-2 {
            hw-head-id = <2>;
            timing-id = <0>;
            connector-id = <2>;
         };
         dpy-3 {
            hw-head-id = <3>;
            timing-id = <0>;
            connector-id = <2>;
         };
         dpy-4 {
            hw-head-id = <4>;
            timing-id = <0>;
            connector-id = <3>;
         };
         dpy-5 {
            hw-head-id = <5>;
            timing-id = <0>;
            connector-id = <3>;
         };
   };
   heads {
         head-0 {
            hw-head-id = <0>;
         };
         head-1 {
            hw-head-id = <1>;
         };
         head-2 {
            hw-head-id = <2>;
         };
         head-3 {
            hw-head-id = <3>;
         };
         head-4 {
            hw-head-id = <4>;
         };
         head-5 {
            hw-head-id = <5>;
         };
   };
   connectors {
      connector-0 {
          connector-id = <0>;
          serializer-data-id = <0>;
      };
      connector-1 {
          connector-id = <1>;
          serializer-data-id = <1>;
      };
      connector-2 {
          connector-id = <2>;
          serializer-data-id = <2>;
      };
  };
};

Properties#

  • dpys: Node consisting of all dpys
    • dpy-<>: dpy subnode provding mapping.

      • hw-head-id: Head utilized by this dpyid

      • timing-id: Timings utilized by this dpyid

      • connector-id: connector utilized by this dpyid

  • heads: Node consisting of all heads
    • head-<>: head subnode providing head id

      • hw-head-id: ID of this head node

  • connectors: Node consisting of all physical connectors
    • connector-<>connector subnode providing connector details

      • connector-id: ID of this connector node

      • serializer-data-id: ID of the serializer data node used by this connector

tegra264-p3960-disp-serializer.dtsi

display@8808c00000 {
   serializers {
      serializer-0 {
         serializer-data-id = <0>;
         maxLinkBW = <0xa>;
         maxLaneCount = <4>;
         supportsMST = <0>;
         supportsDSC = <0>;
         supportsFEC = <0>;
      };
      serializer-1 {
         serializer-data-id = <1>;
         maxLinkBW = <0x1e>;
         maxLaneCount = <4>;
         supportsMST = <0>;
         supportsDSC = <0>;
         supportsFEC = <0>;
      };
      serializer-2 {
         serializer-data-id = <2>;
         maxLinkBW = <0x1e>;
         maxLaneCount = <4>;
         supportsMST = <0>;
         supportsDSC = <0>;
         supportsFEC = <0>;
      };
   };
};

Properties#

  • serializers: Node consisting of all serializer connector nodes
    • serializer-<>: serializer subnode provding mapping and enabled properties.

      • serializer-data-id: Serializer ID of this serializer subnode

      • maxLinkBW: Maximum link bandwidth supported

      • maxLaneCount: Maximum lane count supported

      • supportsMST: MST is enabled is the value is 1 else disabled

      • supportsDSC: DSC is enabled is the value is 1 else disabled

      • supportsFEC: FEC is enabled is the value is 1 else disabled

On this page