From: Miguel Aguilar <miguel.aguilar@ridgerun.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.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: [PATCH 2/2] Davinci: DM365: Enable DaVinci Voice Codec support for DM365 EVM
Date: Mon, 11 Jan 2010 09:53:43 -0600 [thread overview]
Message-ID: <4B4B4987.1080507@ridgerun.com> (raw)
In-Reply-To: <20100111153458.GA2661@rakim.wolfsonmicro.main>
Mark Brown wrote:
> On Mon, Jan 11, 2010 at 09:11:19AM -0600, Miguel Aguilar wrote:
>> Mark Brown wrote:
>
>>>> Can you check the part of this patch related to registering both
>>>> codecs AIC3x and the voice codec?
>
>>> Like I say that all looks fine to me but I can't really check if the
>>> DaVinci code is idiomatic.
>
>> Is there any way to tell alsamixer to use the controls of one
>> subdevice or the other?
>
> Not from the arch/arm stuff, but that's a machine driver issue anyway.
> If you really only want to use a single device then just don't hook up
> the other device in the machine driver and it'll never appear.
Do you think that I still using the approach of having both codecs registered in
the same kernel? or should I get back to the initial approach of selecting the
wanted codec from the configuration menu?
next prev parent reply other threads:[~2010-01-11 15:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 22:17 [PATCH 2/2] Davinci: DM365: Enable DaVinci Voice Codec support for DM365 EVM miguel.aguilar
2010-01-08 11:31 ` Mark Brown
2010-01-08 17:36 ` Miguel Aguilar
2010-01-08 19:37 ` Mark Brown
2010-01-11 15:11 ` Miguel Aguilar
2010-01-11 15:34 ` Mark Brown
2010-01-11 15:53 ` Miguel Aguilar [this message]
2010-01-11 16:21 ` Mark Brown
2010-01-19 20:47 ` Miguel Aguilar
2010-01-19 22:10 ` Mark Brown
2010-01-20 14:32 ` Miguel Aguilar
2010-01-20 15:01 ` Mark Brown
2010-01-11 16:04 ` Kevin Hilman
2010-01-11 16:08 ` Miguel Aguilar
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=4B4B4987.1080507@ridgerun.com \
--to=miguel.aguilar@ridgerun.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=clark.becker@ridgerun.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=diego.dompe@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.