From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Patrick Lai <plai@codeaurora.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: Store codec capabilites in alsa
Date: Tue, 30 Oct 2012 18:42:15 +0000 [thread overview]
Message-ID: <20121030184215.GZ4511@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50901A11.80503@codeaurora.org>
[-- Attachment #1.1: Type: text/plain, Size: 353 bytes --]
On Tue, Oct 30, 2012 at 11:18:57AM -0700, Patrick Lai wrote:
> 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.
Why does the CPU driver want to update the filters in the CODEC? Can't
the application do this?
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2012-10-30 18:42 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
2012-10-30 18:42 ` Mark Brown [this message]
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=20121030184215.GZ4511@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=plai@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 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).