From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Oliver Neukum <oliver@neukum.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
linux-input@vger.kernel.org, linux-hotplug@vger.kernel.org,
USB list <linux-usb@vger.kernel.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Problems with remote-wakeup settings
Date: Fri, 5 Mar 2010 23:04:49 +0100 [thread overview]
Message-ID: <201003052304.49261.rjw@sisk.pl> (raw)
In-Reply-To: <201003052208.09486.oliver@neukum.org>
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.
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-05 22:04 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 [this message]
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
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=201003052304.49261.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=stern@rowland.harvard.edu \
/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).