From: Ricardo Neri <ricardo.neri@ti.com>
To: "Gabriel M. Beddingfield" <gabrbedd@gmail.com>
Cc: alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: Declaring HDMI channel allocation to kernel
Date: Tue, 24 Jul 2012 12:43:43 -0500 [thread overview]
Message-ID: <500EDECF.5000902@ti.com> (raw)
In-Reply-To: <500E9565.2040102@gmail.com>
Hi Gabriel,
On 07/24/2012 07:30 AM, Gabriel M. Beddingfield wrote:
> On 07/23/2012 02:39 PM, Pierre-Louis Bossart wrote:
>> On 7/23/2012 9:18 AM, Gabriel M. Beddingfield wrote:
>>>
>>> Is there an established way for me (from userspace) to pass the HDMI
>>> Channel Allocation (1 byte) to the driver? If not, can you recommend
>>> an approach?
> [snip[
>> I believe this is one of the topics that will be presented by Takashi at
>> LPC, we need the ability to specify a arbitrary sink-specific channel
>> mapping.
>
> OK, thanks! So then, to do this today I need to add my own special sauce.
FWIW, in the past I could use the route plugin to achieve arbitrary
channel mapping. This was done by SW, though. The details are here:
http://mailman.alsa-project.org/pipermail/alsa-devel/2012-April/051573.html
Ricardo
>
> -gabriel
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2012-07-24 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 14:18 Declaring HDMI channel allocation to kernel Gabriel M. Beddingfield
2012-07-23 19:39 ` Pierre-Louis Bossart
2012-07-24 12:30 ` Gabriel M. Beddingfield
2012-07-24 17:43 ` Ricardo Neri [this message]
2012-07-24 18:55 ` Gabriel Beddingfield
2012-07-25 3:10 ` Ricardo Neri
2012-07-24 12:33 ` Takashi Iwai
2012-07-24 12:36 ` Mark Brown
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=500EDECF.5000902@ti.com \
--to=ricardo.neri@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=gabrbedd@gmail.com \
--cc=pierre-louis.bossart@linux.intel.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.