From: Liam Girdwood <lrg@ti.com>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: soc-dsp programming model for loopbacks
Date: Thu, 02 Feb 2012 11:17:52 +0000 [thread overview]
Message-ID: <1328181472.3974.5.camel@odin> (raw)
In-Reply-To: <CABS+qY2GADPO+wkmDf5hzT7uaH7v1zNrdAGKnLbip-QAL8V_RQ@mail.gmail.com>
On Wed, 2012-02-01 at 11:50 +0000, Girdwood, Liam wrote:
> On 1 February 2012 09:07, Vinod Koul <vinod.koul@linux.intel.com> wrote:
> > On Wed, 2012-01-25 at 17:07 +0000, Liam Girdwood 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 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).
> > Hi,
> > Sorry to join the party late :-)
> >
>
No worries ;-)
>
> > Liam, if we configure the hw_params in the machine driver statically,
> > represent the DSP using a map along with a codec kind of modeling.
> >
In OMAP we reconfigure (or fixup) some of the hw_params() in the machine
driver for a BE DAI link that cant operate at the requested FE params.
The ABE takes care of any conversion though.
> > Would the BEs be triggered on from soc_dsp_runtime_update() when the
> > loopback is established thru the DSP.
> > This way we avoid all the "virtual" FEs. Use loopback to turn on codec
> > and DSP (thru BEs)
> >
> > Would this make sense, or I need more coffee :)
In the code base atm we have to use a FE pcm to trigger the BE loopback
DAIs. however, the intention is to use Mark's CODEC <-> CODEC DAI link
work to support the loopback with hard coded params in the machine
driver. This would save the need for any FE pcm operations.
Regards
Liam
> >
> > --
> > ~Vinod
> >
>
next prev parent reply other threads:[~2012-02-02 11:17 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
2012-02-01 9:07 ` Vinod Koul
[not found] ` <CABS+qY2GADPO+wkmDf5hzT7uaH7v1zNrdAGKnLbip-QAL8V_RQ@mail.gmail.com>
2012-02-02 11:17 ` Liam Girdwood [this message]
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=1328181472.3974.5.camel@odin \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=vinod.koul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.