diff options
author | Hans de Goede <hdegoede@redhat.com> | 2010-04-23 05:26:42 -0400 |
---|---|---|
committer | Takashi Iwai <tiwai@suse.de> | 2010-04-23 17:09:46 +0200 |
commit | eb581adf25fe9e42197e591926de85459e68b9fd (patch) | |
tree | 9967f82156d9ab138c96adefa4771a420470fabe /arch/blackfin/include/asm/mmu_context.h | |
parent | 20133d4cd329af7a02ee5af36bba1796d5ff7b1d (diff) | |
download | linux-eb581adf25fe9e42197e591926de85459e68b9fd.tar.bz2 |
ALSA: snd-maestro3: Make hardware volume buttons an input device (rev2)
While working on the sound suspend / resume problems with my laptop
I noticed that the hardware volume handling code in essence just detects
key presses, and then does some hardcoded modification of the master volume
based on which key is pressed.
This made me think that clearly the right thing to do here is just report
these keypresses to userspace and let userspace decide what to with them.
This patch adds a Kconfig option which when enabled reports the volume
buttons as keypresses using an input device. When enabled this option
also gets rid of the ugly direct ac97 writes from the tasklet, the ac97lock
and the need for using a tasklet in general.
As an added bonus the keys now work identical to volume keys on a (usb)
keyboard with multimedia keys, providing visual feedback of the volume
level change, and a better range of the volume control (with a properly
configured desktop environment).
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'arch/blackfin/include/asm/mmu_context.h')
0 files changed, 0 insertions, 0 deletions