From: Clemens Ladisch <clemens@ladisch.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: Multiple channels mapping
Date: Wed, 08 Feb 2012 12:32:17 +0100 [thread overview]
Message-ID: <4F325D41.50304@ladisch.de> (raw)
In-Reply-To: <s5hvcnhllum.wl%tiwai@suse.de>
Takashi Iwai wrote:
> Clemens Ladisch wrote:
>> Takashi Iwai wrote:
>>> Currently the channel-mapping information is a missing piece in ALSA
>>> framework, and it's a very long-standing item on my TODO list.
>>>
>>> The implementation itself should be easy, but the only question is the
>>> API design. If you have a good proposal, please speak up.
>>
>> TLVs on media controller entities.
>
> Well, my concern is that it might be too far from the other PCM
> stuff. How the implementation would look like?
There is one media controller device node per device (= ALSA card),
containing multiple entities (similar to how a ctl device contains
multiple controls). /dev/media42 _is_ separate, but the entity that
represents a PCM device is handled by the PCM code, so it would be
possible to have a shortcut to get a PCM device's TLVs directly.
> More question is whether this information should be available before
> or after hw_params setup.
This is pretty much static information, which is available even when the
PCM device isn't opened.
> BTW, the channel-mapping info can be useful for the automatic plug
> layer, too.
And if there is a need for channel mapping information of ALSA plugins,
there needs to be a userspace library for the media controller API.
Regards,
Clemens
next prev parent reply other threads:[~2012-02-08 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 1:02 Multiple channels mapping Patrick Lai
2012-02-08 8:58 ` Takashi Iwai
2012-02-08 9:18 ` Clemens Ladisch
2012-02-08 9:23 ` Takashi Iwai
2012-02-08 11:32 ` Clemens Ladisch [this message]
2012-02-10 11:05 ` Takashi Iwai
2012-02-08 11:54 ` 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=4F325D41.50304@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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.