Lines Matching +full:audio +full:- +full:graph

2 Dynamic Audio Power Management for Portable Devices
8 Dynamic Audio Power Management (DAPM) is designed to allow portable
9 Linux devices to use the minimum amount of power within the audio
11 management frameworks and, as such, can easily co-exist with them.
16 switching decisions based upon any audio stream (capture/playback)
17 activity and audio mixer settings within the device.
21 * a **widget** is every part of the audio hardware that can be enabled by
27 audio routing graph. This graph is specific to each sound card and spans
32 The graph for the STM32MP1-DK1 sound card is shown in picture:
34 .. kernel-figure:: dapm-graph.svg
35 :alt: Example DAPM graph
38 You can also generate compatible graph for your sound card using
39 `tools/sound/dapm-graph` utility.
47 VREF, VMID (core codec and audio power)
60 audio subsystem signal paths
75 Audio DAPM widgets fall into a number of types:
104 External regulator that supplies power to audio components.
106 External clock that supplies clock to audio components.
108 Audio Interface Input (with TDM slot mask).
110 Audio Interface Output (with TDM slot mask).
114 Digital Audio Interface Input.
116 Digital Audio Interface Output.
124 Inter widget audio data buffer within a DSP.
129 Widget that performs an audio processing effect.
135 Widget that encodes audio data from one format (usually PCM) to another
138 Widget that decodes audio data from a compressed format to an
142 (Widgets are defined in include/sound/soc-dapm.h)
145 There are convenience macros defined in soc-dapm.h that can be used to quickly
153 ---------------------
182 -------------------
184 Path domain widgets have a ability to control or affect the audio signal or
185 audio paths within the audio subsystem. They have the following form:
211 ----------------------
215 machine audio component (non codec or DSP) that can be independently
237 -------------------
245 ---------------
247 Sometimes widgets exist in the codec or machine audio graph that don't have any
249 a virtual widget - a widget with no control bits e.g.
296 separate widgets and routes arrays implementing the case-specific features
305 audio paths (called interconnections). Each interconnection must be defined in
306 order to create a graph of all audio paths between widgets.
309 audio system), as it requires joining widgets together via their audio signal
320 name. We can now connect the destination widget (wrt audio signal) with its
348 -------------------------------
365 An endpoint is a start or end point (widget) of an audio signal within the
374 Endpoints are added to the DAPM graph so that their usage can be determined in
404 See soc-dapm.h for all other widgets that support events.
408 -----------
417 #define SND_SOC_DAPM_PRE_REG 0x10 /* before audio path setup */
418 #define SND_SOC_DAPM_POST_REG 0x20 /* after audio path setup */