devicetree/bindings/graph.txt

4 ---------------
7 control flow to devices, but there can be more complex connections between
10 There already is a simple directed graph between devices tree nodes using
12 can not be inferred from device tree parent-child relationships. The device
22 Documentation/devicetree/bindings/media/video-interfaces.txt.
23 Here the ports describe data interfaces, and the links between them are
28 -----------------------------------
30 Ports are described by child 'port' nodes contained in the device node.
34 If more than one port is present in a device node or there is more than one
36 hardware interface, a common scheme using '#address-cells', '#size-cells'
41         #address-cells = <1>;
42         #size-cells = <0>;
45 	        #address-cells = <1>;
46 	        #size-cells = <0>;
67 allows to specify #address-cells, #size-cells properties for the 'port'
74                 #address-cells = <1>;
75                 #size-cells = <0>;
87 Links between endpoints
88 -----------------------
90 Each endpoint should contain a 'remote-endpoint' phandle property that points
91 to the corresponding endpoint in the port of the remote device. In turn, the
92 remote endpoint should contain a 'remote-endpoint' property. If it has one, it
94 their 'remote-endpoint' phandles pointing at each other form a link between the
97 device-1 {
100                         remote-endpoint = <&device_2_input>;
105 device-2 {
108                         remote-endpoint = <&device_1_output>;
114 -------------------
117 property present in the port and/or endpoint nodes then the following
118 properties are required in a relevant parent node:
120  - #address-cells : number of cells required to define port/endpoint
122  - #size-cells    : should be zero.
125 ----------------------------
127 - remote-endpoint: phandle to an 'endpoint' subnode of a remote device node.