Re: soc-dsp programming model for loopbacks

[Mark Brown <broonie@opensource.wolfsonmicro.com>]

[-- Attachment #1.1: Type: text/plain, Size: 948 bytes --]

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.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]