Searched full:graph (Results 1 – 25 of 95) sorted by relevance
1234
| /Documentation/devicetree/bindings/sound/ |
| D | audio-graph-card.txt | 1 Audio Graph Card:
3 Audio Graph Card specifies audio DAI connections of SoC <-> codec.
5 see ${LINUX}/Documentation/devicetree/bindings/graph.txt
7 Basically, Audio Graph Card property is same as Simple Card.
29 - compatible : "audio-graph-card";
40 compatible = "audio-graph-card";
71 compatible = "audio-graph-card";
143 compatible = "audio-graph-card";
180 compatible = "audio-graph-card";
193 audio-graph-card,prefix = "codec";
[all …]
|
| D | st,stm32-spdifrx.txt | 21 graph.txt.
54 compatible = "audio-graph-card";
|
| D | st,stm32-i2s.txt | 28 graph.txt.
32 compatible = "audio-graph-card";
|
| /Documentation/media/uapi/mediactl/ |
| D | media-controller-model.rst | 17 hardware devices and Linux Kernel interfaces are modelled as graph
18 objects on an oriented graph. The object types that constitute the graph
27 - An **interface** is a graph representation of a Linux Kernel
29 controls one or more entities in the graph.
|
| D | media-ioc-g-topology.rst | 19 MEDIA_IOC_G_TOPOLOGY - Enumerate the graph topology and graph element properties
50 the graph elements that are desired, putting the pointers to them at the
55 desired arrays with the media graph elements.
68 - Version of the media graph topology. When the graph is created,
69 this field starts with zero. Every time a graph element is added
74 - Number of entities in the graph
89 - Number of interfaces in the graph
104 - Total number of pads in the graph
118 - Total number of data and interface links in the graph
303 smaller than the actual number of elements inside the graph. This
|
| /Documentation/media/kapi/ |
| D | mc-core.rst | 18 modelled as an oriented graph of building blocks called entities connected
137 Graph traversal
140 The media framework provides APIs to iterate over entities in a graph.
155 Drivers might also need to iterate over all entities in a graph that can be
157 framework provides a depth-first graph traversal API for that purpose.
162 supported by the graph traversal API. To prevent infinite loops, the graph
166 Drivers initiate a graph traversal by calling
169 The graph structure, provided by the caller, is initialized to start graph
175 When the graph traversal is complete the function will return ``NULL``.
177 Graph traversal can be interrupted at any moment. No cleanup function call
[all …]
|
| /Documentation/devicetree/bindings/connector/ |
| D | samsung,usb-connector-11pin.txt | 15 - any data bus to the connector should be modeled using the OF graph bindings
16 specified in bindings/graph.txt, unless the bus is between parent node and
18 has assigned OF graph port number as follows:
|
| /Documentation/devicetree/bindings/display/connector/ |
| D | vga-connector.txt | 15 The VGA connector internal connections are modeled using the OF graph bindings
16 specified in Documentation/devicetree/bindings/graph.txt.
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | adi,adv7123.txt | 18 graph bindings specified in Documentation/devicetree/bindings/graph.txt.
|
| D | ti,ths813x.txt | 18 graph bindings specified in Documentation/devicetree/bindings/graph.txt.
|
| D | dumb-vga-dac.txt | 14 graph bindings specified in Documentation/devicetree/bindings/graph.txt.
|
| D | ti,ds90c185.txt | 21 graph bindings specified in Documentation/devicetree/bindings/graph.txt.
|
| D | sii902x.txt | 37 simple-card or audio-graph-card binding. See their binding
41 Documentation/devicetree/bindings/sound/audio-graph-card.txt
42 Note: In case of the audio-graph-card binding the used port
|
| D | dw_hdmi.txt | 31 expressed in using ports as specified in the device graph bindings defined
32 in Documentation/devicetree/bindings/graph.txt. The numbering of the ports
|
| D | lvds-transmitter.txt | 34 graph bindings specified in Documentation/devicetree/bindings/graph.txt.
|
| D | thine,thc63lvd1024.txt | 21 to OF graph bindings specified by Documentation/devicetree/bindings/graph.txt
|
| /Documentation/sound/soc/ |
| D | dpcm.rst | 15 graph representing the DSP internal audio paths and uses the mixer settings to
123 3. Define widget graph connections.
264 Widget graph connections
267 The BE DAI links will normally be connected to the graph at initialisation time
286 2. DAPM graph showing DSP audio routing from FE DAIs to BEs.
288 3. DAPM widgets from DSP graph.
304 The BE AIF are used to connect the DSP graph to the graphs for the other
305 component drivers (e.g. codec graph).
335 is enabled or disabled by the state of the DAPM graph. This usually means
340 graph. Control is then carried out by the FE as regular PCM operations.
[all …]
|
| /Documentation/devicetree/bindings/display/hisilicon/ |
| D | dw-dsi.txt | 15 See Documentation/devicetree/bindings/graph.txt for more device graph info.
|
| D | hisi-ade.txt | 29 See Documentation/devicetree/bindings/graph.txt for more device graph info.
|
| /Documentation/doc-guide/ |
| D | hello.dot | 1 graph G {
|
| /Documentation/devicetree/bindings/display/ |
| D | truly,nt35597.txt | 21 are modeled using the OF graph bindings specified in
22 Documentation/devicetree/bindings/graph.txt.
|
| D | arm,hdlcd.txt | 21 using the OF graph bindings specified in
22 Documentation/devicetree/bindings/graph.txt.
|
| D | arm,malidp.txt | 32 is modelled using the OF graph bindings specified in
33 Documentation/devicetree/bindings/graph.txt
|
| /Documentation/devicetree/bindings/ |
| D | graph.txt | 9 arbitrarily complex graph.
10 There already is a simple directed graph between devices tree nodes using
13 tree graph bindings described herein abstract more complex devices that can
|
| /Documentation/devicetree/bindings/display/rockchip/ |
| D | rockchip-lvds.txt | 29 Their connections are modeled using the OF graph bindings specified in
30 Documentation/devicetree/bindings/graph.txt.
|
1234