From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Wang, Jane" <jwang@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"peter.ujfalusi@nokia.com" <peter.ujfalusi@nokia.com>
Subject: Re: [PATCH]ASoc:ZOOM2:Add support for DSP rendering.
Date: Tue, 10 Nov 2009 13:03:34 +0000 [thread overview]
Message-ID: <20091110130334.GC16200@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <13B9B4C6EF24D648824FF11BE8967162039B8D1913@dlee02.ent.ti.com>
On Mon, Nov 09, 2009 at 11:22:47AM -0600, Wang, Jane wrote:
Please fix your MUA to word wrap your mails; it makes them very much
more legible and easy to reply to.
> The scenario is data is going between DSP<->McBSP<->TWL4030. DSP
> configures and controls McBSP ports. Since DSP does not have control
> over TWl4030 codec, the role of ALSA here is providing mixer controls
> for user space application to configure codec to prepare for DSP
> rendering.
So in this setup the DSP is essentially a separate device on the audio
bus; it's very much similar to things like the bluetooth chipset you can
see in the OpenMoko devices and ought to be presented in a similar way
as a separate DAI.
> TWL4030 driver does not provide explicit controls over DAC/ADC, mic
> bias, APLL, headset pop-noise attenuation etc, and we need these to make
> playback/capture happen. I can think of two ways to handle this, one is
> add controls in codec to explicitly control these widgets, or using DAPM
> stream events as a single control to power up/down the path. And I feel
> the second solution is cleaner...
Representing the DSP DAI to ASoC is what's needed here, check out the
OpenMoko code for an example of solving a similar problem.
next prev parent reply other threads:[~2009-11-10 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1257459691-12411-1-git-send-email-jwang@ti.com>
2009-11-06 14:03 ` [PATCH]ASoc:ZOOM2:Add support for DSP rendering Mark Brown
2009-11-09 17:22 ` Wang, Jane
2009-11-10 13:03 ` Mark Brown [this message]
2009-11-11 8:38 ` Peter Ujfalusi
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=20091110130334.GC16200@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jwang@ti.com \
--cc=peter.ujfalusi@nokia.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