mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
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>
Subject: Re: Problems with remote-wakeup settings
Date: Fri, 5 Mar 2010 22:08:09 +0100	[thread overview]
Message-ID: <201003052208.09486.oliver@neukum.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1003051546370.1384-100000@iolanthe.rowland.org>

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

  reply	other threads:[~2010-03-05 21:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 16:23 Alan Stern
2010-03-05 20:38 ` Rafael J. Wysocki
2010-03-05 20:59   ` Alan Stern
2010-03-05 21:08     ` Oliver Neukum [this message]
2010-03-05 22:04       ` Rafael J. Wysocki
2010-03-06  4:16         ` Alan Stern
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=201003052208.09486.oliver@neukum.org \
    --to=oliver@neukum.org \
    --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=rjw@sisk.pl \
    --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

all inboxes | Powered by JetHome®