Lines Matching refs:BE

46 supports 6 back end (BE) DAIs. Each FE PCM can digitally route audio data to any
47 of the BE DAIs. The FE PCM devices can also route audio to more than 1 BE DAI.
115  1) Define the FE and BE DAI links.
117  2) Define any FE/BE PCM operations.
122 1 FE and BE DAI links
141 For the example above we have to define 4 FE DAI links and 6 BE DAI links. The
156 	.....< other FE and BE DAI links here >
167 The FE DAI above sets the codec and code DAIs to dummy devices since the BE is
170 The BE DAIs are configured as follows :-
188 	.....< other BE DAI links here >
191 This BE DAI link connects DAI0 to the codec (in this case RT5460 AIF1). It sets
192 the "no_pcm" flag to mark it has a BE and sets flags for supported stream
195 The BE has also flags set for ignoring suspend and PM down time. This allows
196 the BE to work in a hostless mode where the host CPU is not transferring data
216 A BE DAI link can also set the codec to a dummy device if the code is a device
219 Likewise a BE DAI can also set a dummy cpu DAI if the CPU DAI is managed by the
223 2 FE/BE PCM operations
226 The BE above also exports some PCM operations and a "fixup" callback. The fixup
228 FE hw params. i.e. the DSP may perform SRC or ASRC from the FE to BE.
260 The BE DAI links will normally be connected to the graph at initialisation time
261 by the ASoC DAPM core. However, if the BE codec or BE DAI is a dummy then this
264 /* BE for codec Headset -  DAI0 is dummy and managed by DSP FW */
286  6) BE AIF widgets.
289 defined for each BE and each stream direction. e.g for BE DAI0 above we would
295 The BE AIF are used to connect the DSP graph to the graphs for the other
330  2) Hostless FE. This FE has a virtual connection to the BE DAI links on the DAPM