Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Clemens Ladisch" <cladisch@fastmail.net>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org,
	Lennart Poettering <mznyfn@0pointer.de>
Subject: Re: Channel mapping
Date: Wed, 21 Nov 2007 16:52:20 +0100	[thread overview]
Message-ID: <1195660340.16225.1222569047@webmail.messagingengine.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0711211621310.8325@tm8103.perex-int.cz>

Jaroslav Kysela wrote:
> On Wed, 21 Nov 2007, Clemens Ladisch wrote:
> > Takashi Iwai wrote:
> > > Yes, querying channel mapping is another missing piece with popular
> > > demand.
> > > 
> > > The implementation would be easy, I guess.  But we have to define the
> > > way to inform this from kernel to user space: whether create a new
> > > ioctl or extend the existing ones (if possible)...
> > 
> > It's just metadata that describes a PCM device, so I think we should use
> > TLV for this.
> > 
> > The existing struct snd_ctl_tlv uses a single integer to identify
> > control elements.  We could restrict control numid's to 31 bits and
> > use the upper bit to signal that this value includes device type and
> > device number in the lower bits, if we want to reuse the same TLV
> > ioctls.

Using a ioctl on the ctl device is difficult if the information is
dependent on the hw_params, so this isn't a good idea.

> We can also encode PCM device / subdevice numbers to data structure. But
> I think that best way is to extend channel_info PCM ioctl (create new 
> version and emulate old one - it should be quite easy to implement).

The channel_info ioctl returns only information about one channel.

I think we should have a more flexible ioctl that also allows us to
describe the PCM device itself (such as volume controls that affect
all channels, or latency information).


Regards,
Clemens

  parent reply	other threads:[~2007-11-21 15:52 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20  0:51 [lennart@poettering.net: Status of ALSA "simple" mixer interface] Lennart Poettering
2007-11-21 11:09 ` Takashi Iwai
2007-11-21 11:11 ` Takashi Iwai
2007-11-21 15:23   ` Clemens Ladisch
2007-11-25 19:56     ` The sense or non-sense of the device listing API (was: Status of ALSA "simple" mixer interface]) Lennart Poettering
2007-11-25 20:38       ` Jaroslav Kysela
2007-11-21 11:14 ` Mono device definition Takashi Iwai
2007-11-21 11:20 ` Analog-SPDIF dup Takashi Iwai
2007-11-21 11:22 ` Softvol controls Takashi Iwai
2007-11-29 23:28   ` Lennart Poettering
2007-11-29 23:46     ` John Utz
2007-11-30  0:08       ` Lennart Poettering
2007-11-30  0:34         ` John Utz
2007-11-30  8:59     ` Takashi Iwai
2007-12-04 15:42       ` Jaroslav Kysela
2007-12-13 10:39         ` Takashi Iwai
2007-12-22 22:54         ` Lennart Poettering
2007-12-23 10:21           ` Jaroslav Kysela
2007-12-22 22:48       ` Lennart Poettering
2007-11-21 11:40 ` Disable conversions Takashi Iwai
2007-11-21 14:29   ` Takashi Iwai
2007-11-21 15:16     ` Jaroslav Kysela
2007-11-21 14:51       ` Takashi Iwai
2007-11-25 20:41   ` Lennart Poettering
2007-11-26 15:55     ` Jaroslav Kysela
2007-12-22 22:37       ` Lennart Poettering
2007-11-21 11:42 ` Channel mapping Takashi Iwai
2007-11-21 15:17   ` Clemens Ladisch
2007-11-21 14:57     ` Takashi Iwai
2007-11-21 15:27     ` Jaroslav Kysela
2007-11-21 15:04       ` Takashi Iwai
2007-11-27 16:54         ` Takashi Iwai
2007-11-21 15:52       ` Clemens Ladisch [this message]
2007-11-21 15:36         ` Takashi Iwai
2007-11-21 18:37           ` Jaroslav Kysela
2007-11-22  9:17             ` Clemens Ladisch
2007-11-22  8:55           ` Clemens Ladisch

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=1195660340.16225.1222569047@webmail.messagingengine.com \
    --to=cladisch@fastmail.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=mznyfn@0pointer.de \
    --cc=perex@perex.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox