From: Rolf Theunissen <rolf.theunissen@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: Hardware events
Date: Tue, 30 Nov 2010 12:48:27 +0100 [thread overview]
Message-ID: <4CF4E48B.3030600@gmail.com> (raw)
In-Reply-To: <4CF4B112.3070705@ladisch.de>
Clemens Ladisch wrote:
> Rolf Theunissen wrote:
>
>> For some hardware devices (for instance the ThinkPad EC) the volume can
>> be changed by (only) hardware buttons.
>> ...
>> This raises the following question: is it possible to detect the events
>> originating from the hardware in the functions that handle the callbacks
>> (set via snd_mixer_elem_set_callback/snd_hctl_elem_set_callback)? This
>> would allow to implement an OSD that only responds to the hardware
>> buttons and that would ignore events originating from "software".
>>
> The control notifications are for all changes of the control.
>
> If it is not possible to change the volume in software, then the driver
> must not set the control to be writable.
>
>
> Regards,
> Clemens
>
The issue is not that the driver should be writable or not. Even, if the
volume is read only, an OSD can be shown for any event. However when the
volume can be set both in hardware and in software, the end-user will
expect different behavior.
For instance, if the user changes the volume in a music player
application, no OSD should be shown as this clutters the interface. But
if the volume is changed from the hardware a OSD should be shown.
I don't know if a ticket should be opened for this issue.
Regards,
Rolf
next prev parent reply other threads:[~2010-11-30 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 11:54 Hardware events Rolf Theunissen
2010-11-30 8:08 ` Clemens Ladisch
2010-11-30 11:48 ` Rolf Theunissen [this message]
2010-12-02 7:51 ` 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=4CF4E48B.3030600@gmail.com \
--to=rolf.theunissen@gmail.com \
--cc=alsa-devel@alsa-project.org \
/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.