From: Jaroslav Kysela <perex@perex.cz>
To: alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>
Subject: Re: [RFC] Channel mapping API
Date: Tue, 21 Aug 2012 14:31:55 +0200 [thread overview]
Message-ID: <50337FBB.4020709@perex.cz> (raw)
In-Reply-To: <s5hipcc30h4.wl%tiwai@suse.de>
Date 21.8.2012 14:15, Takashi Iwai wrote:
> For getting the channel map, the driver could send a notification once
> when routing is changed.
This leads to this question: Why you define the map controls volatile?
I think that the channel map changes can be tracked nicely using the
standard control event notifications without any hidden changes.
Perhaps, the value change event may be invoked each time after prepare
and when the user space set the new values and also in above situation,
when the channel map is changed on an external request.
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project; Red Hat, Inc.
next prev parent reply other threads:[~2012-08-21 12:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 10:31 [RFC] Channel mapping API Takashi Iwai
2012-08-21 11:24 ` David Henningsson
2012-08-21 11:44 ` Clemens Ladisch
2012-08-21 12:06 ` Takashi Iwai
2012-08-21 13:13 ` Takashi Iwai
2012-08-21 11:37 ` Clemens Ladisch
2012-08-21 12:15 ` Takashi Iwai
2012-08-21 12:31 ` Jaroslav Kysela [this message]
2012-08-21 12:35 ` Takashi Iwai
2012-08-21 13:14 ` Takashi Iwai
2012-08-21 14:00 ` David Henningsson
2012-08-21 14:06 ` Mark Brown
2012-08-21 14:13 ` David Henningsson
2012-08-21 14:18 ` Mark Brown
2012-08-21 14:49 ` Takashi Iwai
2012-08-21 15:38 ` Clemens Ladisch
2012-08-21 16:27 ` Mark Brown
2012-08-21 17:05 ` Takashi Iwai
2012-08-21 17:11 ` Mark Brown
2012-08-21 19:29 ` Takashi Iwai
2012-08-21 15:49 ` Mark Brown
2012-08-21 14:52 ` David Henningsson
2012-08-21 15:07 ` Mark Brown
2012-08-21 15:38 ` David Henningsson
2012-08-21 16:34 ` Mark Brown
2012-08-21 17:09 ` Takashi Iwai
2012-08-21 17:57 ` Mark Brown
2012-08-21 13:59 ` Mark Brown
2012-08-21 14:08 ` Takashi Iwai
2012-08-21 14:12 ` Mark Brown
2012-08-21 18:03 ` Pierre-Louis Bossart
2012-08-21 19:23 ` Takashi Iwai
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=50337FBB.4020709@perex.cz \
--to=perex@perex.cz \
--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.