[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120216223305.GA1231@opensource.wolfsonmicro.com>
Date: Thu, 16 Feb 2012 14:33:06 -0800
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Arve Hjønnevåg <arve@...roid.com>,
linux-input@...r.kernel.org, linux-pm@...r.kernel.org,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Matthew Garrett <mjg@...hat.com>,
Chase Douglas <chase.douglas@...onical.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Input: Add ioctl to block suspend while event queue is
not empty.
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.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists