From: Miguel Aguilar <miguel.aguilar@ridgerun.com>
To: Steve Chen <schen@mvista.com>
Cc: Santiago Nunez <santiago.nunez@ridgerun.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
clarkbecker <clark.becker@ridgerun.com>
Subject: Re: [PATCH 0/5] Add Voice Codec support for DaVinci platforms
Date: Thu, 21 Jan 2010 13:18:43 -0600 [thread overview]
Message-ID: <4B58A893.1050804@ridgerun.com> (raw)
In-Reply-To: <1264099975.3207.176.camel@linux-1lbu>
Steve,
I'm not sure that this is the same case, please take a look into this thread
between Mark and me, where I pointed the problem in the machine driver for
handling the two codecs:
>Hi Mark,
>
>I have a specific doubt about the codec_dev element snd_soc_device struct of
>the DM365 EVM.
>
>Since I have two codecs on the EVM, I have two snd_soc_codec_device structures:
>
> * AIC3x
>
> struct snd_soc_codec_device soc_codec_dev_aic3x = {
> .probe = aic3x_probe,
> .remove = aic3x_remove,
> .suspend = aic3x_suspend,
> .resume = aic3x_resume,
>};
>
>* Voice Codec
>
>struct snd_soc_codec_device soc_codec_dev_cq93vc = {
> .probe = cq93vc_probe,
> .remove = cq93vc_remove,
> .suspend = cq93vc_suspend,
> .resume = cq93vc_resume,
>};
>
>But I can set only one at a time in the dm365_evm_snd_devdata:
>
>/* evm audio subsystem */
>static struct snd_soc_device dm365_evm_snd_devdata = {
> .card = &dm365_snd_soc_card_evm,
>***
> .codec_dev = &soc_codec_dev_aic3x,
>or
> .codec_dev = &soc_codec_dev_cq93vc,
>***
> .codec_data = &aic3x_setup,
>};
>
>So in case what is the proper way to do this?
>
>Thanks,
>
>Miguel Aguilar
Mark's answer:
On Tue, Jan 19, 2010 at 02:47:16PM -0600, Miguel Aguilar wrote:
> > But I can set only one at a time in the dm365_evm_snd_devdata:
> > ...
> > So in case what is the proper way to do this?
>For now use an ifdef in the machine driver. There's some work due to
>begin fairly shortly (I've CCed in my co-maintainer Liam who's actually
>going to be doing the work) to allow multiple CODECs to work
>simultaneously, if you put the ifdef in the machine driver now then it
>should be straightforward to update the machine driver to make use of
>this new feature when it's ready.
Regards,
Miguel Aguilar
Steve Chen wrote:
> On Thu, 2010-01-21 at 11:35 -0600, Miguel Aguilar wrote:
>> Hi,
>>
>> The following patch series adds support for the Voice Codec in the Davinci
>> platform and in this particular case for the DM365 EVM.
>>
>> The DM365 EVM has two codecs the AIC3x and the Voice Codec, however at this
>> point is not possible to have both enabled simultaneously since the soc-core
>> doesn't support that, so a patch for enable both simultaneously will be sent
>> when this support is available in the soc-core.
>
> I thought, perhaps incorrectly, that soc-core already has the ability to
> support multiple codecs. When I worked on ALSA soc support for DM6467,
> one of the McASP was connected to AIC3x and the other is SPDIF output.
> Both interface can work at the same time. I just assumed that if we
> have two McASP (or other audio controllers) connected to two codecs.
> They would both just work under ALSA soc. Please let me know if I'm
> mistaken.
>
> Thanks,
>
> Steve
>
next prev parent reply other threads:[~2010-01-21 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 17:35 [PATCH 0/5] Add Voice Codec support for DaVinci platforms Miguel Aguilar
[not found] ` <4B58904E.4030108-9uBrGCPFOa1Wk0Htik3J/w@public.gmane.org>
2010-01-21 18:52 ` Steve Chen
2010-01-21 19:18 ` Miguel Aguilar [this message]
2010-01-21 19:25 ` Mark Brown
[not found] ` <66B80913-5079-4E5D-8D89-0CE78D02A14C-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2010-01-21 19:36 ` Steve Chen
2010-01-25 12:35 ` 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=4B58A893.1050804@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=santiago.nunez@ridgerun.com \
--cc=schen@mvista.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).