From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@ti.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:11:12 +0000 [thread overview]
Message-ID: <20120125171112.GR3687@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1327511249.11901.37.camel@odin>
On Wed, Jan 25, 2012 at 05:07:29PM +0000, Liam Girdwood wrote:
> On Tue, 2012-01-24 at 13:36 -0800, Pierre-Louis Bossart wrote:
> We could eventually remove steps 2 and 4 for the FE DAI link, and look
> at hard coding the hw_params() in the mach driver for the loopback link.
That's what the CODEC<->CODEC stuff is all about, hiding the link from
userspace.
> That way the only user space driven actions would be to configure the
> mixers in the CODEC and DSP for the correct route. DAPM would then
> detect the path and Dynamic PCM would use the hard coded configuration
> or bespoke mach driver logic to configure the loopback DAI link based on
> use case. This would have to be done after the basic Dynamic PCM
> infrastructure was upstream though (unless you have a patch atm).
I've sort of got one, tidying it up and pushing it out keeps on being
very near the top of my list but I've never actually got it looking nice
enough for me to actually want to send it out.
next prev parent reply other threads:[~2012-01-25 17:11 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 [this message]
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
[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=20120125171112.GR3687@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.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).