From: Ricardo Neri <ricardo.neri@ti.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Castaneda Gonzalez, Axel" <x0055901@ti.com>,
alsa-devel <alsa-devel@alsa-project.org>,
Ujfalusi <peter.ujfalusi@ti.com>,
"Guiriec, Sebastien" <s-guiriec@ti.com>,
Peter@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Required/preferred multichannel order for ALSA
Date: Thu, 26 Apr 2012 16:33:57 -0500 [thread overview]
Message-ID: <4F99BF45.4020909@ti.com> (raw)
Hi Takashi, list,
I am implementing multichannel support for HDMI on Texas Instruments'
OMAP4. I would like to know if ALSA mandates a specific channel order or
has a preferred one.
I tried to find some guidance in alsa-lib or in the alsa driver. All I
could find is the order described in speaker-test:
FL/FR/RL/RR/C/LFE/SL/SR. This order seems to be in use due to historical
reasons [1]. It was also mentioned that an API to set/get the channel
mapping was going to be implemented [2]; I tried to find it without
success. As [1] and [2] are very old posts, I was wondering if the
situation has changed.
My question arises from the fact that HDMI audio uses the channel
ordering defined in CEA-861 section 6.6.2, which is different from what
speaker-test expects. This also different from the order that SMPTE 320M
specifies. OMAP4 is able to alter the channel mapping, so I could match
what ALSA expects if such required/preferred order exists.
Thanks in advance for your comments.
Ricardo
[1].http://www.spinics.net/lists/alsa-devel/msg24444.html
[2].http://www.spinics.net/lists/alsa-devel/msg24495.html
next reply other threads:[~2012-04-26 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 21:33 Ricardo Neri [this message]
2012-04-27 9:21 ` Required/preferred multichannel order for ALSA Liam Girdwood
2012-04-27 9:57 ` Mark Brown
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=4F99BF45.4020909@ti.com \
--to=ricardo.neri@ti.com \
--cc=Peter@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@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.