From: Liam Girdwood <lrg@ti.com>
To: Patrick Lai <plai@codeaurora.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
"waiw@codeaurora.org" <waiw@codeaurora.org>,
pl bossart <bossart.nospam@gmail.com>,
"asishb@codeaurora.org" <asishb@codeaurora.org>,
"jaywang@codeaurora.org" <jaywang@codeaurora.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: soc-dsp questions
Date: Mon, 13 Jun 2011 18:49:51 +0100 [thread overview]
Message-ID: <4DF64DBF.4020908@ti.com> (raw)
In-Reply-To: <4DF2C2BD.6050505@codeaurora.org>
On 11/06/11 02:19, Patrick Lai wrote:
> On 6/10/2011 2:42 AM, Mark Brown wrote:
>
>>
>> That might be handlable by either of the methods I was suggesting above.
>> Of course depending on the algorithms you're running the DSP may want
>> more mics than it's producing output channels - beam forming or noise
>> cancellation are the obvious examples there.
>
> Yes, exactly.
>
>> Do you mean not also a concern? I *believe* OMAP is passing the
>> configuration through to the external DAI using the front end/back end
>> connection so the format gets selected by the app when it does a record,
>
This is correct. We pass configuration from the FE PCM to all the connected BE DAIs.
Liam
next prev parent reply other threads:[~2011-06-13 17:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 22:01 soc-dsp questions pl bossart
2011-04-26 9:41 ` Liam Girdwood
2011-04-26 10:18 ` Mark Brown
2011-06-10 6:58 ` Patrick Lai
2011-06-10 9:42 ` Mark Brown
2011-06-11 1:19 ` Patrick Lai
2011-06-11 11:48 ` Mark Brown
2011-06-13 4:55 ` Patrick Lai
2011-06-13 18:01 ` Liam Girdwood
2011-06-13 17:55 ` Liam Girdwood
2011-06-13 17:49 ` Liam Girdwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-11-08 8:22 Vinod Koul
2011-11-08 20:20 ` Girdwood, Liam
2011-11-09 8:04 ` Vinod Koul
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=4DF64DBF.4020908@ti.com \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=asishb@codeaurora.org \
--cc=bossart.nospam@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jaywang@codeaurora.org \
--cc=lrg@slimlogic.co.uk \
--cc=plai@codeaurora.org \
--cc=waiw@codeaurora.org \
/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.