From: Patrick Lai <plai@codeaurora.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: Store codec capabilites in alsa
Date: Mon, 29 Oct 2012 20:23:28 -0700 [thread overview]
Message-ID: <508F4830.4010600@codeaurora.org> (raw)
In-Reply-To: <20121029170732.GF4511@opensource.wolfsonmicro.com>
On 10/29/2012 10:07 AM, Mark Brown wrote:
> On Sun, Oct 28, 2012 at 06:13:08PM -0700, Patrick Lai wrote:
>
>> I doubt that ASoC has mechanism for vendor's own CODEC driver to
>> advertise CODEC specific information. However, we would like to
>> check ahead of time before coming up with something on our own.
>
> Unless you tell us something about what's being advertised it's very
> hard to comment;
CODEC has filters for noise cancellation purpose. CPU will need to know
given CODEC has noise cancellation support. Also, CPU needs to know the
CODEC registers to program the filters and which digital audio interface
would have noise reference.
Thanks
Patrick
it's often the case that things are just new rather
> than device specific.
>
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2012-10-30 3:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 2:07 Store codec capabilites in alsa Bharath Ramachandramurthy
2012-10-26 10:45 ` Liam Girdwood
2012-10-29 1:13 ` Patrick Lai
2012-10-29 17:07 ` Mark Brown
2012-10-30 3:23 ` Patrick Lai [this message]
2012-10-30 15:13 ` Mark Brown
2012-10-30 18:18 ` Patrick Lai
2012-10-30 18:42 ` Mark Brown
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=508F4830.4010600@codeaurora.org \
--to=plai@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.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).