Thread (12 messages) flat view 12 messages, 4 authors, 2010-03-06

Re: Problems with remote-wakeup settings

From: Andrey Borzenkov <hidden>
Date: 2010-03-06 04:36:58
Also in: lkml

On Saturday 06 of March 2010 07:16:20 Alan Stern wrote:
On Fri, 5 Mar 2010, Rafael J. Wysocki wrote:
quoted
On Friday 05 March 2010, Oliver Neukum wrote:
quoted
Am Freitag, 5. März 2010 21:59:31 schrieben Sie:
quoted
quoted
I guess it's better if drivers don't set should_wakeup if
unsure, but of course that's impossible to enforce.
That's the real question.  Ideally, drivers won't touch
should_wakeup. How do we get there from here?
Enable it only for devices specifically designed for wakeup, that
is keyboards, power buttons and WoL, perhaps also mice and
modems. Are we far away from that?
I don't think we're very far from that.

Mice are known dangerous, especially the USB ones, though.
I agree, especially for desktop systems.  You don't want the system
to wake up merely because you happened to jostle the mouse.  That
happened to me just a few days ago (and it was a PS/2 mouse, not
USB).
I remember, my old desktop had BIOS option to wake up on mouse click 
(and it had PS/2 mouse either) ignoring mouse move. I actually found it 
useful.

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help