Searched full:endpoint (Results 1 – 25 of 320) sorted by relevance
12345678910>>...13
| /Documentation/devicetree/bindings/sound/ |
| D | audio-graph-card.txt | 48 cpu_endpoint: endpoint {
49 remote-endpoint = <&codec_endpoint>;
60 codec_endpoint: endpoint {
61 remote-endpoint = <&cpu_endpoint>;
83 codec0_endpoint: endpoint {
84 remote-endpoint = <&cpu_endpoint0>;
92 codec1_endpoint: endpoint {
93 remote-endpoint = <&cpu_endpoint1>;
101 codec2_endpoint: endpoint {
102 remote-endpoint = <&cpu_endpoint2>;
[all …]
|
| /Documentation/PCI/endpoint/ |
| D | pci-endpoint.rst | 5 This document is a guide to use the PCI Endpoint Framework in order to create
6 endpoint controller driver, endpoint function driver, and using configfs
19 either in Root Complex mode or Endpoint mode. PCI Endpoint Framework will
20 add endpoint mode support in Linux. This will help to run Linux in an
24 PCI Endpoint Core
27 The PCI Endpoint Core layer comprises 3 components: the Endpoint Controller
28 library, the Endpoint Function library, and the configfs layer to bind the
29 endpoint function with the endpoint controller.
31 PCI Endpoint Controller(EPC) Library
35 in endpoint mode. It also provides APIs to be used by function driver/library
[all …]
|
| D | pci-endpoint-cfs.rst | 4 Configuring PCI Endpoint Using CONFIGFS
9 The PCI Endpoint Core exposes configfs entry (pci_ep) to configure the
10 PCI endpoint function and to bind the endpoint function
11 with the endpoint controller. (For introducing other mechanisms to
12 configure the PCI Endpoint Function refer to [1]).
17 The PCI Endpoint Core layer creates pci_ep directory in the mounted configfs
54 used to configure the standard configuration header of the endpoint function.
91 represent the functions present in the endpoint device.
94 "1" is written to this field, the endpoint device will be ready to
118 [1] :doc:`pci-endpoint`
|
| /Documentation/devicetree/bindings/media/ |
| D | renesas,csi2.yaml | 51 A node containing input and output port nodes with endpoint definitions
59 Input port node, single endpoint describing the CSI-2 transmitter.
65 endpoint:
75 remote-endpoint: true
80 - remote-endpoint
103 "^endpoint@[0-9a-f]$":
110 remote-endpoint: true
114 - remote-endpoint
152 csi20_in: endpoint {
155 remote-endpoint = <&adv7482_txb>;
[all …]
|
| D | renesas,vin.yaml | 74 A node containing a parallel input with a single endpoint definitions as
79 endpoint:
109 remote-endpoint: true
112 - remote-endpoint
128 A node containing input nodes with endpoint definitions as documented in
135 Input port node, single endpoint describing a parallel input source.
141 endpoint:
171 remote-endpoint: true
174 - remote-endpoint
179 - endpoint
[all …]
|
| D | cdns,csi2rx.txt | 38 in the design.Since there is only one endpoint per port,
61 csi2rx_in_sensor: endpoint {
62 remote-endpoint = <&sensor_out_csi2rx>;
71 csi2rx_out_grabber0: endpoint {
72 remote-endpoint = <&grabber0_in_csi2rx>;
79 csi2rx_out_grabber1: endpoint {
80 remote-endpoint = <&grabber1_in_csi2rx>;
87 csi2rx_out_grabber2: endpoint {
88 remote-endpoint = <&grabber2_in_csi2rx>;
95 csi2rx_out_grabber3: endpoint {
[all …]
|
| D | cdns,csi2tx.txt | 38 in the design. Since there is only one endpoint per port,
60 csi2tx_out: endpoint {
61 remote-endpoint = <&remote_in>;
70 csi2tx_in_stream0: endpoint {
71 remote-endpoint = <&stream0_out>;
78 csi2tx_in_stream1: endpoint {
79 remote-endpoint = <&stream1_out>;
86 csi2tx_in_stream2: endpoint {
87 remote-endpoint = <&stream2_out>;
94 csi2tx_in_stream3: endpoint {
[all …]
|
| D | ti,da850-vpif.txt | 20 with child 'endpoint' node. If there are two ports then port@0 must
34 vpif_input_ch0: endpoint@0 {
37 remote-endpoint = <&composite_in>;
40 vpif_input_ch1: endpoint@1 {
48 vpif_output_ch0: endpoint {
50 remote-endpoint = <&composite_out>;
64 composite_in: endpoint {
70 remote-endpoint = <&vpif_input_ch0>;
81 composite_out: endpoint {
85 remote-endpoint = <&vpif_output_ch0>;
[all …]
|
| D | atmel-isi.txt | 14 'port' child node with child 'endpoint' node. Please refer to the bindings
17 Endpoint node properties
24 - remote-endpoint: A phandle to the bus receiver's endpoint node (mandatory).
37 isi_0: endpoint {
38 remote-endpoint = <&ov2640_0>;
60 ov2640_0: endpoint {
61 remote-endpoint = <&isi_0>;
|
| /Documentation/devicetree/bindings/ |
| D | graph.txt | 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
49 endpoint@0 {
53 endpoint@1 {
62 endpoint { ... };
79 endpoint@0 { ... };
80 endpoint@1 { ... };
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
[all …]
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | maxim,max9286.yaml | 57 The connections to the MAX9286 GMSL and its endpoint nodes are modelled
86 endpoint:
90 remote-endpoint:
92 phandle to the remote GMSL source endpoint subnode in the
96 - remote-endpoint
100 - endpoint
110 endpoint:
114 remote-endpoint:
115 description: phandle to the remote CSI-2 sink endpoint.
121 - remote-endpoint
[all …]
|
| D | tvp5150.txt | 29 port must be linked to an endpoint defined in [1]. The port/connector layout is
33 endpoint@0 -----------> Comp0-Con port
34 endpoint@1 ------+----> Svideo-Con port
36 endpoint@1 ------+
37 endpoint@0 -----------> Comp1-Con port
39 endpoint (video bitstream output at YOUT[0-7] parallel bus)
41 Required Endpoint Properties for parallel synchronization on output port:
70 composite0_to_tvp5150: endpoint {
71 remote-endpoint = <&tvp5150_to_composite0>;
82 composite1_to_tvp5150: endpoint {
[all …]
|
| D | ov5640.txt | 25 OV5640 can be connected to a MIPI CSI-2 bus or a parallel bus endpoint.
27 Endpoint node required properties for CSI-2 connection are:
28 - remote-endpoint: a phandle to the bus receiver's endpoint node.
32 Endpoint node required properties for parallel connection are:
33 - remote-endpoint: a phandle to the bus receiver's endpoint node.
61 /* MIPI CSI-2 bus endpoint */
62 ov5640_to_mipi_csi2: endpoint {
63 remote-endpoint = <&mipi_csi2_from_ov5640>;
81 /* Parallel bus endpoint */
82 ov5640_to_parallel: endpoint {
[all …]
|
| /Documentation/devicetree/bindings/display/ |
| D | allwinner,sun8i-r40-tcon-top.yaml | 85 A ports node with endpoint definitions as defined in
87 All ports should have only one endpoint connected to
88 remote endpoint.
100 Input endpoint for Mixer 0 mux.
105 Output endpoint for Mixer 0 mux
117 "^endpoint@[0-9]$":
137 Input endpoint for Mixer 1 mux.
142 Output endpoint for Mixer 1 mux
154 "^endpoint@[0-9]$":
174 Input endpoint for HDMI mux.
[all …]
|
| D | arm,hdlcd.txt | 43 hdlcd_output: endpoint@0 {
44 remote-endpoint = <&hdmi_enc_input>;
56 hdmi_enc_input: endpoint {
57 remote-endpoint = <&hdlcd_output>;
60 hdmi_enc_output: endpoint {
61 remote-endpoint = <&hdmi_1_port>;
72 hdmi_1_port: endpoint {
73 remote-endpoint = <&hdmi_enc_output>;
|
| /Documentation/devicetree/bindings/arm/ |
| D | coresight.txt | 147 by the "bindings/graph.txt", where each "port" along with an "endpoint"
165 etb_in_port: endpoint@0 {
166 remote-endpoint = <&replicator_out_port0>;
180 tpiu_in_port: endpoint@0 {
181 remote-endpoint = <&replicator_out_port1>;
195 etr_in_port: endpoint {
196 remote-endpoint = <&replicator2_out_port0>;
203 etr_out_port: endpoint {
204 remote-endpoint = <&catu_in_port>;
224 replicator_out_port0: endpoint {
[all …]
|
| /Documentation/firmware-guide/acpi/dsd/ |
| D | graph.rst | 38 The port and endpoint concepts are very similar to those in Devicetree
39 [3]. A port represents an interface in a device, and an endpoint
51 data extension key of the endpoint nodes must begin with
52 "endpoint" and must be followed by the "@" character and the number of the
53 endpoint. The object it refers to should be called "EPXY", where "X" is the
54 number of the port and "Y" is the number of the endpoint. An example of such a
57 Package() { "endpoint@0", "EP40" }
60 the number of the port. Each endpoint is similarly numbered with a property
61 extension key "reg", the value of which is the number of the endpoint. Port
62 numbers must be unique within a device and endpoint numbers must be unique
[all …]
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | lontium,lt9611.yaml | 59 "^endpoint(@[0-9])$":
64 remote-endpoint:
81 "^endpoint(@[0-9])$":
86 remote-endpoint:
102 "^endpoint(@[0-9])$":
107 remote-endpoint:
154 lt9611_a: endpoint {
155 remote-endpoint = <&dsi0_out>;
161 lt9611_b: endpoint {
162 remote-endpoint = <&dsi1_out>;
[all …]
|
| D | toshiba,tc358775.yaml | 49 A node containing input and output port nodes with endpoint definitions
62 DSI Input. The remote endpoint phandle should be a
120 d2l_in_test: endpoint {
121 remote-endpoint = <&dsi0_out>;
127 lvds_out: endpoint {
128 remote-endpoint = <&panel_in>;
144 dsi0_out: endpoint {
145 remote-endpoint = <&d2l_in_test>;
179 d2l_in_dual: endpoint {
180 remote-endpoint = <&dsi0_out_dual>;
[all …]
|
| D | toshiba,tc358762.yaml | 49 endpoint:
54 remote-endpoint: true
71 endpoint:
76 remote-endpoint: true
112 bridge_in: endpoint {
113 remote-endpoint = <&dsi_out>;
119 bridge_out: endpoint {
120 remote-endpoint = <&panel_in>;
|
| D | ti,tfp410.yaml | 35 A node containing input and output port nodes with endpoint
49 endpoint:
55 Endpoint sampling edge.
63 Endpoint bus width.
77 endpoint:
115 tfp410_in: endpoint {
118 remote-endpoint = <&dpi_out>;
124 tfp410_out: endpoint {
125 remote-endpoint = <&dvi_connector_in>;
|
| D | renesas,dw-hdmi.txt | 36 sound input of the controller. Each port shall have a single endpoint.
59 dw_hdmi0_in: endpoint {
60 remote-endpoint = <&du_out_hdmi0>;
65 rcar_dw_hdmi0_out: endpoint {
66 remote-endpoint = <&hdmi0_con>;
71 rcar_dw_hdmi0_sound_in: endpoint {
72 remote-endpoint = <&hdmi_sound_out>;
84 hdmi0_con: endpoint {
85 remote-endpoint = <&rcar_dw_hdmi0_out>;
|
| /Documentation/devicetree/bindings/display/ti/ |
| D | ti,omap-dss.txt | 113 tfp410_in: endpoint@0 {
114 remote-endpoint = <&dpi_out>;
121 tfp410_out: endpoint@0 {
122 remote-endpoint = <&dvi_connector_in>;
135 dvi_connector_in: endpoint {
136 remote-endpoint = <&tfp410_out>;
158 tpd12s015_in: endpoint@0 {
159 remote-endpoint = <&hdmi_out>;
166 tpd12s015_out: endpoint@0 {
167 remote-endpoint = <&hdmi_connector_in>;
[all …]
|
| /Documentation/devicetree/bindings/display/rockchip/ |
| D | rockchip-lvds.txt | 36 - video port 0 for the VOP input, the remote endpoint maybe vopb or vopl
47 panel_in_lvds: endpoint {
48 remote-endpoint = <&lvds_out_panel>;
74 lvds_in_vopb: endpoint@0 {
76 remote-endpoint = <&vopb_out_lvds>;
78 lvds_in_vopl: endpoint@1 {
80 remote-endpoint = <&vopl_out_lvds>;
87 lvds_out_panel: endpoint {
88 remote-endpoint = <&panel_in_lvds>;
|
| /Documentation/devicetree/bindings/usb/ |
| D | gr-udc.txt | 17 endpoint related interrupts and one for OUT endpoint related interrupts.
22 from the default size of 1024. The array is indexed by the OUT endpoint
24 each OUT endpoint of the core. Fewer entries overrides the default sizes
28 from the default size of 1024. The array is indexed by the IN endpoint
30 each IN endpoint of the core. Fewer entries overrides the default sizes
|
12345678910>>...13