[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201003052208.09486.oliver@neukum.org>
Date: Fri, 5 Mar 2010 22:08:09 +0100
From: Oliver Neukum <oliver@...kum.org>
To: Alan Stern <stern@...land.harvard.edu>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
"Linux-pm mailing list" <linux-pm@...ts.linux-foundation.org>,
linux-input@...r.kernel.org, linux-hotplug@...r.kernel.org,
USB list <linux-usb@...r.kernel.org>,
Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: Problems with remote-wakeup settings
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?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists