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

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 o=
f 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?

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?

	Regards
		Oliver