From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Arve Hjønnevåg" <arve@android.com>,
linux-input@vger.kernel.org, linux-pm@vger.kernel.org,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Matthew Garrett" <mjg@redhat.com>,
"Chase Douglas" <chase.douglas@canonical.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: Add ioctl to block suspend while event queue is not empty.
Date: Thu, 16 Feb 2012 14:33:06 -0800 [thread overview]
Message-ID: <20120216223305.GA1231@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201202162331.07051.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
On Thu, Feb 16, 2012 at 11:31:06PM +0100, Rafael J. Wysocki wrote:
> Can you actually select what keys may wake up the system from sleep
> (I mean "real sleep", when the whole system is entirely off except for wakeup
> devices)?
Yes, that's often possible. In suspend mode you can get a two stage
process where the wakeup itself is triggered by simply looking for any
electrical activity on a set of pins. This generates a wakeup and an
interrupt for the keypad which then powers up the actual keypad circuit
and looks to see what the keypress was. The Samsung keypad driver in
mainline does this in runtime PM, while no key is pressed the keypad
controller is in suspend mode.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-16 22:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 2:24 [PATCH] Input: Add ioctl to block suspend while event queue is not empty Arve Hjønnevåg
2012-02-11 23:28 ` Rafael J. Wysocki
2012-02-13 23:52 ` Arve Hjønnevåg
2012-02-15 23:51 ` Rafael J. Wysocki
2012-02-16 5:24 ` Arve Hjønnevåg
2012-02-16 22:31 ` Rafael J. Wysocki
2012-02-16 22:33 ` Mark Brown [this message]
2012-02-14 3:25 ` NeilBrown
2012-02-15 23:30 ` Rafael J. Wysocki
2012-02-16 1:53 ` Paul Fox
2012-02-16 21:44 ` Rafael J. Wysocki
2012-02-15 23:18 ` 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=20120216223305.GA1231@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=arve@android.com \
--cc=chase.douglas@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).