alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, 'Liam Girdwood' <lrg@ti.com>
Subject: Re: soc-dsp programming model for loopbacks
Date: Thu, 26 Jan 2012 07:12:07 -0600	[thread overview]
Message-ID: <4F215127.8050509@linux.intel.com> (raw)
In-Reply-To: <20120125201438.GA17032@opensource.wolfsonmicro.com>


>> I can see how this would simplify the loopback part, but doesn't it make the
>> 'regular' playback/capture functionality more complex? If my DSP is seen as
>> a CODEC, how do I represent the CPU-DSP interface (DMA or shared memory)?
>
> You'd need a DAI for that interface but you'll need that no matter what
> you do, it'll just be a very simple DAI that needs no configuration for
> things like AIF format.  With the soc-pcm setup you also need the front
> and back end DAIs so it's about the same, the benefit comes at runtime.
> My primary focus for the CODEC<->CODEC links is actually things like
> basebands rather than on-SoC DSPs, it's just that if the hardware can be
> thought of in the same way it should simplify things a little.

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?
Thanks for your feedback
-Pierre

  reply	other threads:[~2012-01-26 13:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4f1f2489.c602440a.208e.ffff9d7bSMTPIN_ADDED@mx.google.com>
2012-01-25 17:07 ` soc-dsp programming model for loopbacks Liam Girdwood
2012-01-25 17:11   ` Mark Brown
2012-01-25 17:13     ` Liam Girdwood
2012-01-25 17:28       ` Mark Brown
2012-01-25 20:03     ` Pierre-Louis Bossart
     [not found]     ` <002d01ccdb9c$7099f1e0$51cdd5a0$@bossart@linux.intel.com>
2012-01-25 20:14       ` Mark Brown
2012-01-26 13:12         ` Pierre-Louis Bossart [this message]
2012-01-26 14:03           ` Mark Brown
2012-01-26 14:27             ` Liam Girdwood
2012-01-26 14:32               ` Mark Brown
2012-01-26 14:42                 ` Liam Girdwood
2012-02-01  9:07   ` Vinod Koul
     [not found]     ` <CABS+qY2GADPO+wkmDf5hzT7uaH7v1zNrdAGKnLbip-QAL8V_RQ@mail.gmail.com>
2012-02-02 11:17       ` Liam Girdwood
2012-02-02 12:03         ` Vinod Koul
2012-02-02 12:06           ` Mark Brown
2012-02-02 12:18             ` Vinod Koul
2012-02-02 18:15               ` Mark Brown
2012-02-02 18:35           ` Liam Girdwood
     [not found] <007801ccdae0$381fcf40$a85f6dc0$@bossart@linux.intel.com>
2012-01-24 22:00 ` Mark Brown
2012-01-25 17:12   ` Liam Girdwood
2012-01-25 17:20     ` Mark Brown
2012-01-25 17:48       ` Liam Girdwood
2012-01-25 18:05         ` Mark Brown
2012-01-24 21:36 Pierre-Louis Bossart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F215127.8050509@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).