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>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Ujfalusi <peter.ujfalusi@ti.com>,
"Guiriec, Sebastien" <s-guiriec@ti.com>,
Peter@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: Required/preferred multichannel order for ALSA
Date: Sat, 28 Apr 2012 22:23:36 -0500 [thread overview]
Message-ID: <4F9CB438.6050002@ti.com> (raw)
In-Reply-To: <s5hobqdweyg.wl%tiwai@suse.de>
Thanks to everyone for replying!
On 04/27/2012 07:12 AM, Takashi Iwai wrote:
> At Fri, 27 Apr 2012 10:21:37 +0100,
> Liam Girdwood wrote:
>>
>> On Thu, 2012-04-26 at 16:33 -0500, Ricardo Neri wrote:
>>> 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
>>
>> 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.
>>
>> This seems like it would be a good subject for the BoF.
>
> Yes. As I added to LPC 2012 wiki page, it's a topic I'd like to
> discuss in the audio microconf, too. It's a long-standing issue,
> not only for embedded devices but also PCs, especially with HDMI/DP.
>
> Actually I've had a few different (partial) implementations, but
> nothing was so convincing yet.
>
> BTW, for the time being, the remapping itself is done in alsa-lib
> route plugin. This works when the driver is unique and supports
> only a single configuration. Then you can define the routing table
> beforehand. Take a look at alsa-lib/src/conf/cards/*.conf based on
> old AC97 codecs.
Thanks for the advice! I could remap the channels succesfully with the
alsa-lib route plugin. It increased the CPU usage when using
speaker-test, though; from 2% to ~5%, according to top. I guess this is
acceptable for now.
>
> OTOH, if the driver is generic (e.g. HD-audio) and supports different
> configurations, it doesn't work so easily. A more generic API is
> mandatory in such a case.
Maybe I can statically remap the channels in the driver to align with
speaker-test and post in omappedia how to remap if someone needs to.
This in case their HDMI sinks supports a different HDMI layout.
Thanks!
Ricardo
>
>
> Takashi
prev parent reply other threads:[~2012-04-29 3:23 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
2012-04-27 12:12 ` Takashi Iwai
2012-04-29 3:23 ` Ricardo Neri [this message]
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=4F9CB438.6050002@ti.com \
--to=ricardo.neri@ti.com \
--cc=Peter@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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.