From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Daniel Drake <dsd@laptop.org>,
linux-input@vger.kernel.org, linux-pm@lists.linux-foundation.org,
rjw@sisk.pl, dilinger@queued.net
Subject: Re: [PATCH v4 1/2] Input: enable i8042-level wakeup control
Date: Wed, 03 Aug 2011 16:12:12 +0800 [thread overview]
Message-ID: <4E3902DC.9040006@cn.fujitsu.com> (raw)
In-Reply-To: <20110803065920.GC23399@core.coreip.homeip.net>
On 08/03/2011 02:59 PM, Dmitry Torokhov wrote:
> Hi Daniel,
>
> On Tue, Aug 02, 2011 at 04:49:15PM +0100, Daniel Drake wrote:
>> The OLPC XO laptop is able to use the PS/2 controller as a wakeup source.
>> When used as a wakeup source, the key press/mouse motion must not be lost.
>>
>> Add infrastructure to allow controllers to be marked as wakeup-capable,
>> and avoid doing power control/reset on the i8042/serio/input devices when
>> running in this mode. For systems where this functionality is available,
>> you are expected to enable wakeups on the i8042 device, the serio
>> devices, and the relevant input devices, to ensure that the hardware is
>> left powered and untouched throughout the suspend/resume.
>>
>> Signed-off-by: Daniel Drake<dsd@laptop.org>
>> ---
>> drivers/input/input.c | 6 +++-
>> drivers/input/keyboard/atkbd.c | 4 ++-
>> drivers/input/mouse/hgpk.c | 2 +
>> drivers/input/mouse/psmouse-base.c | 4 ++-
>> drivers/input/serio/i8042-io.h | 4 ++
>> drivers/input/serio/i8042-ip22io.h | 4 ++
>> drivers/input/serio/i8042-jazzio.h | 4 ++
>> drivers/input/serio/i8042-ppcio.h | 4 ++
>> drivers/input/serio/i8042-snirm.h | 4 ++
>> drivers/input/serio/i8042-sparcio.h | 4 ++
>> drivers/input/serio/i8042-x86ia64io.h | 4 ++
>> drivers/input/serio/i8042.c | 62 +++++++++++++++++++++++++++++---
>> drivers/input/serio/serio.c | 29 +++++++++++++--
>> 13 files changed, 122 insertions(+), 13 deletions(-)
>>
>> serio->port_data = port;
>> - serio->dev.parent =&i8042_platform_device->dev;
>> + serio->dev.parent = parent;
>> + device_set_wakeup_capable(&serio->dev, device_can_wakeup(parent));
>> if (idx< 0) {
>> strlcpy(serio->name, "i8042 AUX port", sizeof(serio->name));
>> strlcpy(serio->phys, I8042_AUX_PHYS_DESC, sizeof(serio->phys));
>> @@ -1403,6 +1450,9 @@ static int __init i8042_probe(struct platform_device *dev)
>> i8042_dritek_enable();
>> #endif
>>
>> + if (i8042_enable_wakeup)
>> + device_set_wakeup_capable(&dev->dev, true);
>> +
>
> device_set_wakeup_capable(&dev->dev, i8042_enable_wakeup); ?
>
Hi Daniel:
May be you missed this comment by Dmitry?
Thanks
Best Regards
Wanlong Gao
next prev parent reply other threads:[~2011-08-03 8:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 15:49 [PATCH v4 1/2] Input: enable i8042-level wakeup control Daniel Drake
2011-08-03 6:59 ` Dmitry Torokhov
2011-08-03 8:04 ` Daniel Drake
2011-08-03 18:43 ` Dmitry Torokhov
2011-08-03 19:24 ` Daniel Drake
2011-08-03 19:38 ` Dmitry Torokhov
2011-08-03 19:51 ` Daniel Drake
2011-08-05 15:24 ` Daniel Drake
2011-08-11 18:02 ` Daniel Drake
2011-08-17 7:03 ` Dmitry Torokhov
2011-09-03 12:45 ` Daniel Drake
2011-08-03 8:12 ` Wanlong Gao [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-02 15:49 Daniel Drake
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=4E3902DC.9040006@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=dilinger@queued.net \
--cc=dmitry.torokhov@gmail.com \
--cc=dsd@laptop.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--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).