From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Castaneda Gonzalez, Axel" <x0055901@ti.com>,
alsa-devel <alsa-devel@alsa-project.org>,
Ricardo Neri <ricardo.neri@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
"Guiriec, Sebastien" <s-guiriec@ti.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: Required/preferred multichannel order for ALSA
Date: Fri, 27 Apr 2012 13:22:26 +0100 [thread overview]
Message-ID: <20120427122225.GG18260@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <s5hmx5xwete.wl%tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 700 bytes --]
On Fri, Apr 27, 2012 at 02:15:57PM +0200, Takashi Iwai wrote:
> Mark Brown wrote:
> > As well as being able to reorder things there's also the cases where a
> > multi-channel link can be assigned to send several independant streams
> > rather than actually be a multi-channel link.
> True. OTOH, separating to different streams can be done mostly
> without extra configuration. The driver may neeed to handle the
> open/close race, but basically splitting can be done uniquely just by
> the number of channels. Of course, there might be other excpetions
> and corner cases, though.
Yes, I think it's mostly just a slight generalisation of the same
problem from an implementation point of view.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-04-27 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 21:33 Required/preferred multichannel order for ALSA Ricardo Neri
2012-04-27 9:21 ` Liam Girdwood
2012-04-27 9:57 ` Mark Brown
2012-04-27 12:15 ` Takashi Iwai
2012-04-27 12:22 ` Mark Brown [this message]
2012-04-27 12:12 ` Takashi Iwai
2012-04-29 3:23 ` Ricardo Neri
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=20120427122225.GG18260@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=ricardo.neri@ti.com \
--cc=s-guiriec@ti.com \
--cc=tiwai@suse.de \
--cc=x0055901@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.