Home
last modified time | relevance | path

Searched full:graph (Results 1 – 25 of 102) sorted by relevance

12345

/Documentation/userspace-api/media/mediactl/
Dmedia-controller-model.rst10 hardware devices and Linux Kernel interfaces are modelled as graph
11 objects on an oriented graph. The object types that constitute the graph
20 - An **interface** is a graph representation of a Linux Kernel
22 controls one or more entities in the graph.
Dmedia-ioc-g-topology.rst13 MEDIA_IOC_G_TOPOLOGY - Enumerate the graph topology and graph element properties
42 the graph elements that are desired, putting the pointers to them at the
47 desired arrays with the media graph elements.
60 - Version of the media graph topology. When the graph is created,
61 this field starts with zero. Every time a graph element is added
66 - Number of entities in the graph
81 - Number of interfaces in the graph
96 - Total number of pads in the graph
110 - Total number of data and interface links in the graph
290 smaller than the actual number of elements inside the graph. This
/Documentation/devicetree/bindings/sound/
Daudio-graph-card.txt1 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 …]
/Documentation/driver-api/media/
Dmc-core.rst18 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/display/
Dingenic,lcd.yaml42 description: OF graph bindings (specified in bindings/graph.txt).
45 description: OF graph bindings (specified in bindings/graph.txt).
Dingenic,ipu.yaml36 description: OF graph bindings (specified in bindings/graph.txt).
Dtruly,nt35597.txt21 are modeled using the OF graph bindings specified in
22 Documentation/devicetree/bindings/graph.txt.
Darm,hdlcd.txt21 using the OF graph bindings specified in
22 Documentation/devicetree/bindings/graph.txt.
Darm,malidp.txt32 is modelled using the OF graph bindings specified in
33 Documentation/devicetree/bindings/graph.txt
Darm,komeda.txt28 modeled using the OF graph bindings specified in
29 Documentation/devicetree/bindings/graph.txt
Dmipi-dsi-bus.txt70 using the graph bindings [1], [2].
78 The graph bindings should be used to represent the multiple DSI busses that are
82 [1] Documentation/devicetree/bindings/graph.txt
90 DSI host using of-graph bindings.
/Documentation/devicetree/bindings/arm/
Dete.yaml22 with any optional connection graph as per the coresight bindings.
40 $ref: /schemas/graph.yaml#/properties/ports
44 $ref: /schemas/graph.yaml#/properties/port required:
/Documentation/devicetree/bindings/display/bridge/
Dsii902x.txt39 simple-card or audio-graph-card binding. See their binding
43 Documentation/devicetree/bindings/sound/audio-graph-card.txt
44 Note: In case of the audio-graph-card binding the used port
Ddw_hdmi.txt31 expressed in using ports as specified in the device graph bindings defined
32 in Documentation/devicetree/bindings/graph.txt. The numbering of the ports
Dsimple-bridge.yaml36 OF graph bindings specified in Documentation/devicetree/bindings/graph.txt.
/Documentation/sound/soc/
Ddpcm.rst15 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/
Ddw-dsi.txt15 See Documentation/devicetree/bindings/graph.txt for more device graph info.
Dhisi-ade.txt29 See Documentation/devicetree/bindings/graph.txt for more device graph info.
/Documentation/doc-guide/
Dhello.dot1 graph G {
/Documentation/devicetree/bindings/usb/
Dti,hd3ss3220.yaml29 description: OF graph bindings (specified in bindings/graph.txt) that model
/Documentation/devicetree/bindings/
Dgraph.txt9 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/atmel/
Dhlcdc-dc.txt15 to external devices using the OF graph reprensentation (see ../graph.txt).
/Documentation/devicetree/bindings/display/rockchip/
Drockchip-lvds.txt33 Their connections are modeled using the OF graph bindings specified in
34 Documentation/devicetree/bindings/graph.txt.
/Documentation/firmware-guide/acpi/
Dindex.rst11 dsd/graph
/Documentation/devicetree/bindings/display/imx/
Dldb.txt47 Each LVDS Channel has to contain either an of graph link to a panel device node
54 Documentation/devicetree/bindings/graph.txt.
94 /* Using an of-graph endpoint link to connect the panel */

12345