Lines Matching +full:remote +full:- +full:endpoint
4 ---------------
12 can not be inferred from device tree parent-child relationships. The device
22 Documentation/devicetree/bindings/media/video-interfaces.txt.
28 -----------------------------------
31 Each port node contains an 'endpoint' subnode for each remote device port
33 remote device, an 'endpoint' child node must be provided for each link.
35 endpoint at a port, or a port node needs to be associated with a selected
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>;
49 endpoint@0 {
53 endpoint@1 {
62 endpoint { ... };
67 allows to specify #address-cells, #size-cells properties for the 'port'
74 #address-cells = <1>;
75 #size-cells = <0>;
79 endpoint@0 { ... };
80 endpoint@1 { ... };
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
93 must not point to anything other than the local endpoint. Two endpoints with
94 their 'remote-endpoint' phandles pointing at each other form a link between the
97 device-1 {
99 device_1_output: endpoint {
100 remote-endpoint = <&device_2_input>;
105 device-2 {
107 device_2_input: endpoint {
108 remote-endpoint = <&device_1_output>;
114 -------------------
116 If there is more than one 'port' or more than one 'endpoint' node or 'reg'
117 property present in the port and/or endpoint nodes then the following
120 - #address-cells : number of cells required to define port/endpoint
122 - #size-cells : should be zero.
124 Optional endpoint properties
125 ----------------------------
127 - remote-endpoint: phandle to an 'endpoint' subnode of a remote device node.