alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH v2] davinci-mcasp: Add support for multichannel playback
Date: Fri, 08 Mar 2013 08:29:49 +0100	[thread overview]
Message-ID: <5139936D.9080001@topic.nl> (raw)
In-Reply-To: <B5906170F1614E41A8A28DE3B8D121433ED3D448@DBDE01.ent.ti.com>

On 03/06/2013 12:19 PM, Bedia, Vaibhav wrote:
> On Wed, Mar 06, 2013 at 16:27:15, Mark Brown wrote:
>> On Wed, Mar 06, 2013 at 10:54:52AM +0000, Bedia, Vaibhav wrote:
>>
>>> 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.
>>
>>> Mark, Liam,
>>
>>> Any suggestions?
>>
>> Nobody with any interest in such systems has stepped up to work on the
>> framework, and of course relatively little CPU hardware supports
>> multiple streams on a single DAI.
>>
>
> Ok. Thinking more on this I guess the situation I described above will indeed be a rare
> case. There would be additional complexity in ensuring that the codecs are always operating
> in sync. It would perhaps be simpler to cascade the codecs (if supported) and use only one
> interface to transfer the data. Or just use multichannel codec like Michal and Daniel
> are doing.

I have 9 codecs connected, and the main problem to solve was to get the 
system to start ALL of them instead of just one.

I solved that by creating a "multiplex" codec, which in itself doesn't 
do anything. It exports a mixer where you can switch on/off the codecs 
you want to use, and it forwards all commands (_ops) to the codecs that 
are enabled. The serializer settings are sent to the asp driver as if 
they are TDM masks (using the bits to enable serializers instead).

In userland you see 10 codecs, you can use each separately, or use the 
10th codec (the multiplexer) to use any combination of other codecs.

-- 
Mike Looijmans - Topic Automation

  reply	other threads:[~2013-03-08  7:29 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 [this message]
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
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=5139936D.9080001@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=alsa-devel@alsa-project.org \
    /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).