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: Tue, 30 Oct 2012 11:18:57 -0700 [thread overview]
Message-ID: <50901A11.80503@codeaurora.org> (raw)
In-Reply-To: <20121030151303.GS4511@opensource.wolfsonmicro.com>
On 10/30/2012 8:13 AM, Mark Brown wrote:
> On Mon, Oct 29, 2012 at 08:23:28PM -0700, Patrick Lai wrote:
>> On 10/29/2012 10:07 AM, Mark Brown wrote:
>
>>> 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.
>
> Why is this all not just normal configuration done from the application
> layer? Especially the noise reference configuration just looks like
> totally normal routing configuration.
>
Agree that for noise reference can be done through normal routing
configuration. However, CPU driver does not normally manage CODEC
register. In my case, CPU algorithm module needs to know what CODEC
registers to program in order to update the filters.
So far, ASoC model has partitioned roles of CPU and CODEC to be managed
by CPU driver and CODEC driver. Both drivers talk on common interface
to allow easy swap out of CPU hardware or CODEC hardware. In our case,
the requirement described so far requires tight coupling of CPU and
CODEC. We are looking to maintain clean partition while meeting the
requirement through ASoc framework.
>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
--
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 18:19 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
2012-10-30 15:13 ` Mark Brown
2012-10-30 18:18 ` Patrick Lai [this message]
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=50901A11.80503@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).