On Mon, 8 Jun 2009, Ingo Molnar wrote:
> > For example do you really need every key pressed while the screen
> > saver is running or is it enough for the keyboard to be able to
> > generate a wakeup event?
> The sane default here is to suspend the keyboard, except if an audio
> app is running that binds to the volume keys of the keyboard.
> If the 'keyboard' is properly abstracted in the kernel and the
> kernel driver _knows_ that the volume keys are in use, this is not a
> problem.
So, if you want to abstract this properly, you are proposing that the
application should in some sense "bind to keyboard keys"?
That has several drawbacks:
- applications in the current universe don't do that
- it's awful overhead:
+ it apparently wouldn't have any other use than for waking up from
autosuspended mode (possibly while screensaver is running)
+ I believe that application writers will find it a little boring to
have to start all their main() functions with explicit eunumeration of
the keys the application is expecting :)
- even if we require applications to do so, there will be ones violating
this rule (i.e. kernel only knows what userspace tells him, in this
situation ... is this reliable enough?)
To sum it up -- I don't think that what you are proposing will work.
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
