From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Miguel Aguilar <miguel.aguilar@ridgerun.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
clark.becker@ridgerun.com, santiago.nunez@ridgerun.com,
diego.dompe@ridgerun.com, alsa-devel@alsa-project.org,
nsnehaprabha@ti.com, todd.fischer@ridgerun.com
Subject: Re: Handling two audio codec in the same kernel
Date: Wed, 25 Nov 2009 11:21:01 +0000 [thread overview]
Message-ID: <20091125112100.GA18883@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4B0C0BD5.9050407@ridgerun.com>
On Tue, Nov 24, 2009 at 10:37:41AM -0600, Miguel Aguilar wrote:
> * How is the proper way to register both codecs in the same kernel?
At the minute you can't really. However, if the CODEC for the voice
interface is mostly empty (which I seem to recall was the case?) then
you can skip registering the CODEC and only register the DAI.
> * If I have registered in the same kernel, How I can choose the codec
> that will be used in the alsamixer menu?
The application layer will do this based on which DAI it chooses to play
audio down - each will appear separately to them, as you're doing below.
> The DMA logic works fine as you see in the examples above. However, only
> the AIC works recording/playback, the voice codec doesn't work. If I
> switch the default codec to Voice Codec it works.
Initially I'd suggest testing with hw rather than plughw to make sure
the test is isolated to the drivers.
next prev parent reply other threads:[~2009-11-25 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 19:29 [PATCH 2/4] ASoC: DaVinci: Voice Codec Interface miguel.aguilar
2009-09-22 21:36 ` Mark Brown
2009-09-23 15:18 ` Miguel Aguilar
2009-09-23 15:49 ` Mark Brown
2009-09-23 16:09 ` Miguel Aguilar
2009-09-23 16:39 ` Mark Brown
2009-11-24 16:37 ` Handling two audio codec in the same kernel Miguel Aguilar
2009-11-25 11:21 ` Mark Brown [this message]
[not found] ` <20091125112100.GA18883-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2009-11-25 18:06 ` Narnakaje, Snehaprabha
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=20091125112100.GA18883@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=clark.becker@ridgerun.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=diego.dompe@ridgerun.com \
--cc=miguel.aguilar@ridgerun.com \
--cc=nsnehaprabha@ti.com \
--cc=santiago.nunez@ridgerun.com \
--cc=todd.fischer@ridgerun.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 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.