Lines Matching +full:simple +full:- +full:graph +full:- +full:card
15 graph representing the DSP internal audio paths and uses the mixer settings to
18 DPCM re-uses all the existing component codec, platform and DAI drivers without
23 -------------------------------------
26 document for all examples :-
32 PCM0 <------------> * * <----DAI0-----> Codec Headset
34 PCM1 <------------> * * <----DAI1-----> Codec Speakers
36 PCM2 <------------> * * <----DAI2-----> MODEM
38 PCM3 <------------> * * <----DAI3-----> BT
40 * * <----DAI4-----> DMIC
42 * * <----DAI5-----> FM
45 This diagram shows a simple smart phone audio subsystem. It supports Bluetooth,
47 modem. This sound card exposes 4 DSP front end (FE) ALSA PCM devices and
53 Example - DPCM Switching playback from DAI0 to DAI1
54 ---------------------------------------------------
59 Playback on PCM0 to Headset would look like :-
65 PCM1 <------------> * * <----DAI1-----> Codec Speakers
67 PCM2 <------------> * * <----DAI2-----> MODEM
69 PCM3 <------------> * * <----DAI3-----> BT
71 * * <----DAI4-----> DMIC
73 * * <----DAI5-----> FM
76 The headset is removed from the jack by user so the speakers must now be used :-
80 PCM0 <============> * * <----DAI0-----> Codec Headset
82 PCM1 <------------> * * <====DAI1=====> Codec Speakers
84 PCM2 <------------> * * <----DAI2-----> MODEM
86 PCM3 <------------> * * <----DAI3-----> BT
88 * * <----DAI4-----> DMIC
90 * * <----DAI5-----> FM
93 The audio driver processes this as follows :-
117 except that we also have to :-
123 3. Define widget graph connections.
127 -------------------
133 PCM0 <------------> * * <----DAI0-----> Codec Headset
135 PCM1 <------------> * * <----DAI1-----> Codec Speakers
137 PCM2 <------------> * * <----DAI2-----> MODEM
139 PCM3 <------------> * * <----DAI3-----> BT
141 * * <----DAI4-----> DMIC
143 * * <----DAI5-----> FM
147 FE DAI links are defined as follows :-
155 .platform_name = "dsp-audio",
156 .codec_name = "snd-soc-dummy",
157 .codec_dai_name = "snd-soc-dummy-dai",
176 The BE DAIs are configured as follows :-
183 .cpu_dai_name = "ssp-dai.0",
184 .platform_name = "snd-soc-dummy",
186 .codec_name = "rt5640.0-001c",
187 .codec_dai_name = "rt5640-aif1",
204 like a BT phone call :-
208 PCM0 <------------> * * <----DAI0-----> Codec Headset
210 PCM1 <------------> * * <----DAI1-----> Codec Speakers
212 PCM2 <------------> * * <====DAI2=====> MODEM
214 PCM3 <------------> * * <====DAI3=====> BT
216 * * <----DAI4-----> DMIC
218 * * <----DAI5-----> FM
232 --------------------
253 rate->min = rate->max = 48000;
254 channels->min = channels->max = 2;
264 Widget graph connections
265 ------------------------
267 The BE DAI links will normally be connected to the graph at initialisation time
269 has to be set explicitly in the driver :-
272 /* BE for codec Headset - DAI0 is dummy and managed by DSP FW */
282 implement :-
284 1. Front End PCM DAIs - i.e. struct snd_soc_dai_driver.
286 2. DAPM graph showing DSP audio routing from FE DAIs to BEs.
288 3. DAPM widgets from DSP graph.
298 have :-
304 The BE AIF are used to connect the DSP graph to the graphs for the other
305 component drivers (e.g. codec graph).
316 PCM0 <------------> * * <----DAI0-----> Codec Headset
318 PCM1 <------------> * * <====DAI1=====> Codec Speakers/Mic
320 PCM2 <------------> * * <====DAI2=====> MODEM
322 PCM3 <------------> * * <----DAI3-----> BT
324 * * <----DAI4-----> DMIC
326 * * <----DAI5-----> FM
332 The host can control the hostless link either by :-
334 1. Configuring the link as a CODEC <-> CODEC style link. In this case the link
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.
342 userspace code to control the link. Its recommended to use CODEC<->CODEC
346 CODEC <-> CODEC link
347 --------------------
349 This DAI link is enabled when DAPM detects a valid path within the DAPM graph.
367 .codec_dai_name = "modem-aif1",
382 -----------