Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
	Simon <horms@verge.net.au>, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: Question about TDM "slot"
Date: Fri, 27 Nov 2015 11:36:12 +0000	[thread overview]
Message-ID: <20151127113612.GL1929@sirena.org.uk> (raw)
In-Reply-To: <871tbbsu27.wl%kuninori.morimoto.gx@renesas.com>


[-- Attachment #1.1: Type: text/plain, Size: 556 bytes --]

On Fri, Nov 27, 2015 at 08:55:01AM +0000, Kuninori Morimoto wrote:

> If my understanding was correct, tdm_slots is not enough for me.
> Because my CPU/Codec needs to know 6ch by (6ch) or (2ch + 2ch + 2ch)
> (My CPU can output both style)
> How to select this ?

I think we'd currently expect the three two channel interfaces to appear
as separate DAIs with their own TDM slots, though with routing within
the CPU you could just always configure them as a single DAI and then
let the choice of connection to the front end DAIs select what gets
routed out.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2015-11-27 11:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17  8:49 Question about TDM "slot" Kuninori Morimoto
2015-11-17 10:52 ` Mark Brown
2015-11-18  7:27   ` Kuninori Morimoto
2015-11-18  7:27   ` Kuninori Morimoto
2015-11-18  7:28   ` Kuninori Morimoto
2015-11-18  7:29   ` Kuninori Morimoto
2015-11-18  7:37   ` Kuninori Morimoto
2015-11-18 11:30     ` Mark Brown
2015-11-19  0:33       ` Kuninori Morimoto
2015-11-27  8:55         ` Kuninori Morimoto
2015-11-27 11:36           ` Mark Brown [this message]
2015-11-29 23:49             ` Kuninori Morimoto

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=20151127113612.GL1929@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.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