[alsa-devel] soc-dsp questions
vinod.koul at linux.intel.com
Wed Nov 9 09:04:57 CET 2011
On Tue, 2011-11-08 at 20:20 +0000, Girdwood, Liam wrote:
> Hi Vinod,
> Sorry, just about to travel again so my replies might be delayed.
> On 8 November 2011 08:22, Vinod Koul <vinod.koul at linux.intel.com> wrote:
> > Hey Liam,
> > I had few questions on your dsp work, would be great if you could answer
> > them and help me in understanding the approach.
> > - Is it possible to have one FE connected to multiple BEs (voice FE to
> > modem and headset bBE), if so how?
> yes, the DAPM graph is extended to link the AIF of each FE PCM to each
> supported BE DAI (please look at omap-abe-dsp.c).
> This allows (via kcontrol settings) the routing between FE PCMs and BE
> DAIs to be controlled at stream runtime. The Dynamic PCM core takes
> care of all the PCM ops and hw_params for each DAI (and re-writes any
> params that require changes for a particular DAI).
Good, that is what i was hoping for :)
> > - SND_SOC_DAI_LINK_OPT_HOST, what does this mean, does not seem to be
> > used anywhere in core?
> It's historical and can be removed.
> > - Why comment need dummy codec for some BEs like BT etc, when soc-core
> > has already one?
> > - any reason why be haves a number associated with a BE, than usual
> > convention of referring things by string name in asoc?
> Sorry, not sure what part do you mean here ?
you are referring to BEs using a number of be_id in the dai_link, like
as OMAP_ABE_DAI_XXX. Not usually by the name of the BE DAI. Any reason
for this departure from usual asoc convention of using string names?
> > and last one, when would this be merged to mainline, 3.3?
> Ah yes, the important question ;) I've been traveling the last 3
> months or so and have not had a chance to finish the upstreaming. I
> have one more trip planned this year and my intention is 3.3 when I
Okay, thanks for the info
More information about the Alsa-devel