All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Kristen Carlson Accardi <kristen@linux.intel.com>,
	Linux PM list <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] i8042 / PM: Allow PC keyboard to wake up from suspend-to-idle
Date: Tue, 17 Mar 2015 09:50:33 +0100	[thread overview]
Message-ID: <20150317085033.GC9761@amd> (raw)
In-Reply-To: <1902569.dAVq7nl4i8@vostro.rjw.lan>


> > > Yeah, that works too.  And you're right that there's no reason to do that for
> > > keyboard only.
> > 
> > Actually, are you sure?
> > 
> > Resuming on mouse click is reasonable, resuming on mouse move is not,
> > as table vibrations are likely to cause that.
> 
> This is disabled by default, so user space has to enable it anyway if it wants
> to.

Good. (But still, for suspend-to-RAM, only mouse _click_ will resume
the machine, as the optical sensor is powered down, no?)

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2015-03-17  8:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 15:19 [PATCH] i8042 / PM: Allow PC keyboard to wake up from suspend-to-idle Rafael J. Wysocki
2015-03-09 18:00 ` Dmitry Torokhov
2015-03-09 22:41   ` Rafael J. Wysocki
2015-03-09 23:08     ` Rafael J. Wysocki
2015-03-10  0:05       ` Dmitry Torokhov
2015-03-16 21:11       ` Pavel Machek
2015-03-16 23:20         ` Rafael J. Wysocki
2015-03-17  8:50           ` Pavel Machek [this message]
2015-03-17 14:39             ` 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=20150317085033.GC9761@amd \
    --to=pavel@ucw.cz \
    --cc=dmitry.torokhov@gmail.com \
    --cc=kristen@linux.intel.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.