Lines Matching refs:BE
48 supports 6 back end (BE) DAIs. Each FE PCM can digitally route audio data to any
49 of the BE DAIs. The FE PCM devices can also route audio to more than 1 BE DAI.
119 1. Define the FE and BE DAI links.
121 2. Define any FE/BE PCM operations.
126 FE and BE DAI links
146 For the example above we have to define 4 FE DAI links and 6 BE DAI links. The
162 .....< other FE and BE DAI links here >
173 The FE DAI above sets the codec and code DAIs to dummy devices since the BE is
176 The BE DAIs are configured as follows :-
195 .....< other BE DAI links here >
198 This BE DAI link connects DAI0 to the codec (in this case RT5460 AIF1). It sets
199 the ``no_pcm`` flag to mark it has a BE and sets flags for supported stream
202 The BE has also flags set for ignoring suspend and PM down time. This allows
203 the BE to work in a hostless mode where the host CPU is not transferring data
224 A BE DAI link can also set the codec to a dummy device if the codec is a device
227 Likewise a BE DAI can also set a dummy cpu DAI if the CPU DAI is managed by the
231 FE/BE PCM operations
234 The BE above also exports some PCM operations and a ``fixup`` callback. The fixup
236 FE hw params. i.e. the DSP may perform SRC or ASRC from the FE to BE.
267 The BE DAI links will normally be connected to the graph at initialisation time
268 by the ASoC DAPM core. However, if the BE codec or BE DAI is a dummy then this
272 /* BE for codec Headset - DAI0 is dummy and managed by DSP FW */
294 6. BE AIF widgets.
297 defined for each BE and each stream direction. e.g for BE DAI0 above we would
304 The BE AIF are used to connect the DSP graph to the graphs for the other
339 2. Hostless FE. This FE has a virtual connection to the BE DAI links on the DAPM