From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Rafael J. Wysocki" <rjw@sisk.pl>
Date: Fri, 05 Mar 2010 22:04:49 +0000
Subject: Re: Problems with remote-wakeup settings
Message-Id: <201003052304.49261.rjw@sisk.pl>
List-Id: <linux-hotplug.vger.kernel.org>
References: <Pine.LNX.4.44L0.1003051546370.1384-100000@iolanthe.rowland.org> <201003052208.09486.oliver@neukum.org>
In-Reply-To: <201003052208.09486.oliver@neukum.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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>

On Friday 05 March 2010, Oliver Neukum wrote:
> Am Freitag, 5. M=E4rz 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.
> >=20
> > That's the real question.  Ideally, drivers won't touch should_wakeup. =
=20
> > How do we get there from here?
>=20
> 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