From: Andrey Borzenkov <arvidjaar-JGs/UdohzUI@public.gmane.org>
To: linux-hotplug-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Alan Stern
<stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>,
"Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>,
Oliver Neukum <oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>,
Linux-pm mailing list
<linux-pm-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
USB list <linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Kernel development list
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Problems with remote-wakeup settings
Date: Sat, 6 Mar 2010 07:36:18 +0300 [thread overview]
Message-ID: <201003060736.18555.arvidjaar@mail.ru> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1003052314130.10381-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org>
[-- Attachment #1: Type: Text/Plain, Size: 1161 bytes --]
On Saturday 06 of March 2010 07:16:20 Alan Stern wrote:
> On Fri, 5 Mar 2010, Rafael J. Wysocki wrote:
> > On Friday 05 March 2010, Oliver Neukum wrote:
> > > Am Freitag, 5. März 2010 21:59:31 schrieben Sie:
> > > > > 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.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-06 4:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 16:23 Problems with remote-wakeup settings Alan Stern
2010-03-05 20:38 ` Rafael J. Wysocki
[not found] ` <201003052138.53647.rjw-KKrjLPT3xs0@public.gmane.org>
2010-03-05 20:59 ` Alan Stern
2010-03-05 21:08 ` Oliver Neukum
2010-03-05 22:04 ` Rafael J. Wysocki
2010-03-06 4:16 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1003052314130.10381-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org>
2010-03-06 4:36 ` Andrey Borzenkov [this message]
2010-03-05 21:59 ` Rafael J. Wysocki
2010-03-06 4:34 ` Alan Stern
2010-03-06 20:54 ` Rafael J. Wysocki
2010-03-06 21:05 ` Alan Stern
2010-03-06 21:25 ` Rafael J. Wysocki
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=201003060736.18555.arvidjaar@mail.ru \
--to=arvidjaar-jgs/udohzui@public.gmane.org \
--cc=linux-hotplug-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-pm-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org \
--cc=rjw-KKrjLPT3xs0@public.gmane.org \
--cc=stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).