[alsa-devel] soc-dsp programming model for loopbacks

Liam Girdwood lrg at ti.com
Thu Jan 26 15:27:48 CET 2012

On Thu, 2012-01-26 at 14:03 +0000, Mark Brown wrote:
> On Thu, Jan 26, 2012 at 07:12:07AM -0600, Pierre-Louis Bossart wrote:
> > Bear with me here, I am still somewhat confused.
> > - Liam suggested either a hard-coded DAI configuration or machine
> > driver logic to remove the need for virtual front-ends
> > - Mark suggested to consider the DSP as a CODEC with some work to
> > re-implement the host-dsp interface.
> > Is this CODEC<->CODEC solution on top of the Dynamic PCM patches? Or
> > are we talking about two completely different approaches?
> The two are orthogonal to each other but complimenary.  Like I say it
> really depends on how your hardware is wired up - it depends on the
> level of isolation that the DSP provides between the CPU and the outside
> world.
> If the system looks like:
>     CPU <-> DSP <-> External
> you should model the DSP as a separate device.  If on the other hand it
> looks more like this:
>    DSP     External
>     ^----v----^
>         CPU
> then soc-pcm is what you're looking for.

Fwiw, the OMAP ABE architecture mixes both above diagrams. We are using
dynamic PCM for managing all the DAI links and will add in support to
use the CODEC <-> CODEC stuff for the loopback DAI interfaces (saving
the need to open()), hw_oparams() etc).



More information about the Alsa-devel mailing list