From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Steve Chen <schen@mvista.com>
Cc: Santiago Nunez <santiago.nunez@ridgerun.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
Miguel Aguilar <miguel.aguilar@ridgerun.com>,
clarkbecker <clark.becker@ridgerun.com>
Subject: Re: [PATCH 0/5] Add Voice Codec support for DaVinci platforms
Date: Thu, 21 Jan 2010 19:25:20 +0000 [thread overview]
Message-ID: <66B80913-5079-4E5D-8D89-0CE78D02A14C@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1264099975.3207.176.camel@linux-1lbu> (sfid-20100121_185231_613114_5A2091DA)
On 21 Jan 2010, at 18:52, Steve Chen <schen@mvista.com> 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.
It can only cope with one CODEC with registers. That S/PDIF interface
has no registers so could be made to work.
next prev parent reply other threads:[~2010-01-21 19:24 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
2010-01-21 19:25 ` Mark Brown [this message]
[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=66B80913-5079-4E5D-8D89-0CE78D02A14C@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=miguel.aguilar@ridgerun.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