From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: soc-dsp programming model for loopbacks
Date: Wed, 25 Jan 2012 17:48:57 +0000	[thread overview]
Message-ID: <1327513737.11901.47.camel@odin> (raw)
In-Reply-To: <20120125172051.GS3687@opensource.wolfsonmicro.com>
On Wed, 2012-01-25 at 17:20 +0000, Mark Brown wrote:
> On Wed, Jan 25, 2012 at 05:12:25PM +0000, Liam Girdwood wrote:
> > On Tue, 2012-01-24 at 22:00 +0000, Mark Brown wrote:
> 
> > > Note that the use of soc-dsp isn't required for on-SoC DSPs - it really
> > > depends on how the hardware looks.  If the DSP external format is very
> > > strongly tied to the format used to DMA to and from main memory (or
> > > other interfaces) then soc-dsp is what you need, if the DSP is able to
> > > rewrite formats more flexibly then it should be more direct to model it
> > > as a CODEC device with whatever number of DAIs and routing between them.
> 
> > It's also needed if your DSP cant control or configure any of your host
> > CPU DAI hardware controllers that it needs to physically use to route
> > audio data.
> 
> Depends how they're allocated - the DSP driver can always do the
> management on behalf of the DSP firmware if the hardware is structured
> in a way that makes that make sense (for example, if the CPU never talks
> to the outside world directly).
Wouldn't that either mean the DSP driver (re)implements some of the CPU
DAI driver operations OR the DSP driver calling the CPU DAI driver ops
directly ? 
Regards
Liam
next prev parent reply	other threads:[~2012-01-25 17:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <007801ccdae0$381fcf40$a85f6dc0$@bossart@linux.intel.com>
2012-01-24 22:00 ` soc-dsp programming model for loopbacks Mark Brown
2012-01-25 17:12   ` Liam Girdwood
2012-01-25 17:20     ` Mark Brown
2012-01-25 17:48       ` Liam Girdwood [this message]
2012-01-25 18:05         ` Mark Brown
     [not found] <4f1f2489.c602440a.208e.ffff9d7bSMTPIN_ADDED@mx.google.com>
2012-01-25 17:07 ` 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
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
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=1327513737.11901.47.camel@odin \
    --to=lrg@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=pierre-louis.bossart@linux.intel.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).