From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@ti.com>
Cc: "Castaneda Gonzalez, Axel" <x0055901@ti.com>,
alsa-devel <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>, Ricardo Neri <ricardo.neri@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
"Guiriec, Sebastien" <s-guiriec@ti.com>
Subject: Re: Required/preferred multichannel order for ALSA
Date: Fri, 27 Apr 2012 10:57:34 +0100 [thread overview]
Message-ID: <20120427095734.GC18260@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1335518497.4150.6.camel@odin>
[-- Attachment #1.1: Type: text/plain, Size: 458 bytes --]
On Fri, Apr 27, 2012 at 10:21:37AM +0100, Liam Girdwood wrote:
> A lot of hardware now can remap channels to suit the use case so it
> would probably be good to have an ALSA API to get/set the mappings.
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.
> This seems like it would be a good subject for the BoF.
Yes.
[-- 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 9:57 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 [this message]
2012-04-27 12:15 ` Takashi Iwai
2012-04-27 12:22 ` Mark Brown
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=20120427095734.GC18260@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 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).