Enabling/disabling input events.

Dmitry Torokhov dtor at insightbb.com
Sat Apr 28 09:05:54 EDT 2007


On Wednesday 25 April 2007 13:24, Zephaniah E. Hull wrote:
> The current trend is for events like power buttons and lid switches to
> be handled through the input subsystem.
> This leaves an odd hole for cases where you wish to set the hardware
> behavior of these buttons, specificly on the OLPC we have several events
> that signal through the input system, which are capable of waking the
> system from suspend mode.  This is not always desirable, so the
> hardware leaves us a way to disable the button/switch completely, but at
> the moment there is no clean kernel interface for this.

Input layer (with the exception of keyboard repeat rate) presently
does not control underlying hardware, this task is left to individual
drivers. For example atkbd is responsible for changing keyboard set,
psmouse is responsible for setting desired report rate and resolution,
control various quirks of IBM trackpoint devices, etc. etc. There are
unlimited number of knobs that may be needed for various devices that
it is impossible to come up with standard interface.

I think enabling/disabling wakeup events belongs with the rest of
knobs in PM (ACPI?) subsystem.


More information about the Devel mailing list