On Fri, 26 Feb 2010, Clemens Ladisch wrote: > > > ALSA sends notifications to all mixer application when the value of > > > any mixer control has changed. To be able to avoid sending them for > > > controls that did not actually change, it uses the return value of the > > > .put callback: 0 means the control value did not change; 1 means it has > > > changed (or might have changed), and a notification is to be sent. > > > <http://www.alsa-project.org/~tiwai/writing-an-alsa-driver/ch06s05.html#control-interface-callbacks-put> > > > > I am looking at it. I think I had it like that on purpose, to trigger an > > OSD when a volume-related hotkey is pressed even if it doesn't change the > > state (mute when already mute, vol down when already at minimum, etc). > > This is not about changes initiated by key presses but changes made > through the ALSA mixer API. Or does the hardware generate a hotkey > event when software changes the volume? The firmware doesn't send events for software changes, mostly because it does not want, or, expect any. These mixers are read-only by default. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
