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: Thu, 26 Jan 2012 14:42:56 +0000 [thread overview]
Message-ID: <1327588976.7134.8.camel@odin> (raw)
In-Reply-To: <20120126143255.GB28994@opensource.wolfsonmicro.com>
On Thu, 2012-01-26 at 14:32 +0000, Mark Brown wrote:
> On Thu, Jan 26, 2012 at 02:27:48PM +0000, Liam Girdwood wrote:
> > On Thu, 2012-01-26 at 14:03 +0000, Mark Brown wrote:
>
> > > CPU <-> DSP <-> External
>
> > > DSP External
> > > ^----v----^
> > > CPU
>
> > 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).
>
> In terms of the data path I think it's pretty much always like the
> second path with the DMA controller owned by Linux driving the data
> between the various components?
Wrt OMAP, the DMA and the ABE can drive data to the component drivers.
Both DMA and ABE only drive data at the request of the CPU (via PCM and
DAI ops).
Regards
Liam
next prev parent reply other threads:[~2012-01-26 14:43 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
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 [this message]
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=1327588976.7134.8.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).