From: Daniel Mack <zonque@gmail.com>
To: "Bedia, Vaibhav" <vaibhav.bedia@ti.com>
Cc: "lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>,
Michal Bachraty <michal.bachraty@streamunlimited.com>
Subject: Re: [PATCH v2] davinci-mcasp: Add support for multichannel playback
Date: Wed, 06 Mar 2013 12:00:48 +0100 [thread overview]
Message-ID: <513721E0.8000605@gmail.com> (raw)
In-Reply-To: <B5906170F1614E41A8A28DE3B8D121433ED3D3ED@DBDE01.ent.ti.com>
On 06.03.2013 11:54, Bedia, Vaibhav wrote:
> Hi Daniel,
>
> On Tue, Mar 05, 2013 at 21:31:59, Daniel Mack wrote:
> [...]
>>
>> As Michal described, we used a board with a multichannel Codec on it,
>> which connects 3 of its I2S inputs to the AM33xx's AXR data lines.
>>
>> Software wise, we tested with 'aplay -cX', and that seems to work just fine.
>>
>
> Since you are using a multichannel codec things are a lot simplified for you :)
> Someone might want to hook up multiple codecs to get multi-channel behavior.
> There will be only 1 CPU DAI but there can be upto 16 CODEC DAIs operating in
> sync. I haven't really followed the recent ASoC changes so I don't know whether
> something like this can be handled right now.
I would rather instanciate multiple McASP cores for such setups, so you
can (in theory) also make them operate on different bit depths and clock
dividers. You think that's possible as well?
Thanks,
Daniel
next prev parent reply other threads:[~2013-03-06 11:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 16:38 [PATCH v2] davinci-mcasp: Add support for multichannel playback Michal Bachraty
2013-03-05 11:06 ` Bedia, Vaibhav
2013-03-05 11:41 ` Michal Bachraty
2013-03-05 12:03 ` Bedia, Vaibhav
2013-03-05 12:24 ` Michal Bachraty
2013-03-05 16:01 ` Daniel Mack
2013-03-06 10:54 ` Bedia, Vaibhav
2013-03-06 10:57 ` Mark Brown
2013-03-06 11:19 ` Bedia, Vaibhav
2013-03-08 7:29 ` Mike Looijmans
2013-03-11 7:01 ` Bedia, Vaibhav
2013-03-11 8:33 ` Mike Looijmans
2013-03-11 8:56 ` Bedia, Vaibhav
2013-04-05 13:21 ` Can DAPM paths span multiple codecs/drivers? Mike Looijmans
2013-04-10 11:08 ` [PATCH v2] davinci-mcasp: Add support for multichannel playback Mike Looijmans
2013-03-06 11:00 ` Daniel Mack [this message]
2013-03-06 11:19 ` Bedia, Vaibhav
2013-03-08 14:22 ` Mike Looijmans
2013-03-11 7:01 ` Bedia, Vaibhav
2013-03-06 14:27 ` Michal Bachraty
2013-03-06 14:31 ` Bedia, Vaibhav
2013-03-06 14:44 ` Michal Bachraty
2013-03-07 11:59 ` Bedia, Vaibhav
2013-03-08 13:11 ` Daniel Mack
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=513721E0.8000605@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lgirdwood@gmail.com \
--cc=michal.bachraty@streamunlimited.com \
--cc=vaibhav.bedia@ti.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).