[alsa-devel] soc-dsp programming model for loopbacks
vinod.koul at linux.intel.com
Wed Feb 1 10:07:11 CET 2012
On Wed, 2012-01-25 at 17:07 +0000, Liam Girdwood wrote:
> We could eventually remove steps 2 and 4 for the FE DAI link, and look
> at hard coding the hw_params() in the mach driver for the loopback
> That way the only user space driven actions would be to configure the
> mixers in the CODEC and DSP for the correct route. DAPM would then
> detect the path and Dynamic PCM would use the hard coded configuration
> or bespoke mach driver logic to configure the loopback DAI link based
> use case. This would have to be done after the basic Dynamic PCM
> infrastructure was upstream though (unless you have a patch atm).
Sorry to join the party late :-)
Liam, if we configure the hw_params in the machine driver statically,
represent the DSP using a map along with a codec kind of modeling.
Would the BEs be triggered on from soc_dsp_runtime_update() when the
loopback is established thru the DSP.
This way we avoid all the "virtual" FEs. Use loopback to turn on codec
and DSP (thru BEs)
Would this make sense, or I need more coffee :)
More information about the Alsa-devel