From: Takashi Iwai <tiwai@suse.de>
To: alsa-devel@alsa-project.org
Subject: [RFC] Channel mapping API
Date: Tue, 21 Aug 2012 12:31:57 +0200 [thread overview]
Message-ID: <s5hr4r0359e.wl%tiwai@suse.de> (raw)
Hi,
this is a progress report of my longstanding TODO, the channel map API
implementation. I'm going to cover this at Plumbers audio uconf, so
we can discuss details there, too.
The channel mapping API provides a method for user-space to query, get
and set the channel map of a PCM stream. It's required for assigning
channels properly for multi-channel streams.
* KERNEL IMPLEMENTATION
In my latest attempt, I implemented with control elements. A control
element is created for each PCM substream with the corresponding
device and substream index. Then it gives a TLV for querying maps, a
read op for obtaining the current map, and optionally a write op for
setting the map. The obvious merit by this way is that no extra
kernel ABI is required.
A couple of new helper functions are provided for assigning standard
channel maps. Currently, HD-audio and AC97 drivers has some
implementation.
* ALSA-LIB IMPLEMENTATION
The additional alsa-lib API functions look like:
int **snd_pcm_query_chmaps(snd_pcm_t *pcm);
int *snd_pcm_get_chmap(snd_pcm_t *pcm);
int snd_pcm_set_chmap(snd_pcm_t *pcm, const int *map);
snd_pcm_query_chmaps() returns the list of channel maps. A channel
map is represented by an integer array, beginning with the channel map
type, followed by the number of channels, and the position of each
channel, e.g.
{ SND_CHMAP_FIXED, 4, SND_CHMAP_FL, SND_CHMAP_FR, SND_CHMAP_RL, SND_CHMAP_RR }
snd_pcm_get_chmap() returns the currently assigned channel map for the
given PCM stream. If the PCM is before prepared, it fills UNKNOWN.
When a driver allows user to change the channel map, user can call
snd_pcm_set_chmap(). For example, HDMI allows you to choose whether
it's 4.0 or 3.1 output.
* RESOURCES
The latest kernel patchset is found in sound-unstable tree
topic/tlv-chmap branch.
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable.git topic/tlv-chmap
The alsa-lib portion is found in a tree on github topic/chmap branch.
git://github.com/tiwai/alsa-lib.git topic/chmap
thanks,
Takashi
next reply other threads:[~2012-08-21 10:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 10:31 Takashi Iwai [this message]
2012-08-21 11:24 ` [RFC] Channel mapping API David Henningsson
2012-08-21 11:44 ` Clemens Ladisch
2012-08-21 12:06 ` Takashi Iwai
2012-08-21 13:13 ` Takashi Iwai
2012-08-21 11:37 ` Clemens Ladisch
2012-08-21 12:15 ` Takashi Iwai
2012-08-21 12:31 ` Jaroslav Kysela
2012-08-21 12:35 ` Takashi Iwai
2012-08-21 13:14 ` Takashi Iwai
2012-08-21 14:00 ` David Henningsson
2012-08-21 14:06 ` Mark Brown
2012-08-21 14:13 ` David Henningsson
2012-08-21 14:18 ` Mark Brown
2012-08-21 14:49 ` Takashi Iwai
2012-08-21 15:38 ` Clemens Ladisch
2012-08-21 16:27 ` Mark Brown
2012-08-21 17:05 ` Takashi Iwai
2012-08-21 17:11 ` Mark Brown
2012-08-21 19:29 ` Takashi Iwai
2012-08-21 15:49 ` Mark Brown
2012-08-21 14:52 ` David Henningsson
2012-08-21 15:07 ` Mark Brown
2012-08-21 15:38 ` David Henningsson
2012-08-21 16:34 ` Mark Brown
2012-08-21 17:09 ` Takashi Iwai
2012-08-21 17:57 ` Mark Brown
2012-08-21 13:59 ` Mark Brown
2012-08-21 14:08 ` Takashi Iwai
2012-08-21 14:12 ` Mark Brown
2012-08-21 18:03 ` Pierre-Louis Bossart
2012-08-21 19:23 ` Takashi Iwai
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=s5hr4r0359e.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--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 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.