From: "Arve Hjønnevåg" <arve@android.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Randy Dunlap" <randy.dunlap@oracle.com>,
linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
"Thadeu Lima de Souza Cascardo" <cascardo@holoscopio.com>,
"Márton Németh" <nm127@freemail.hu>,
"Sven Neumann" <s.neumann@raumfeld.com>,
"Tero Saarni" <tero.saarni@gmail.com>,
"Henrik Rydberg" <rydberg@euromail.se>,
"Matthew Garrett" <mjg@redhat.com>,
"Jiri Kosina" <jkosina@suse.cz>,
linux-input@vger.kernel.org
Subject: Re: [PATCH 8/9] Input: Block suspend while event queue is not empty.
Date: Fri, 23 Apr 2010 22:02:50 -0700 [thread overview]
Message-ID: <z2wd6200be21004232202me5d59908y25bf9523fd62edce@mail.gmail.com> (raw)
In-Reply-To: <201004231408.15885.dmitry.torokhov@gmail.com>
On Fri, Apr 23, 2010 at 2:08 PM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
> On Friday 23 April 2010 01:56:25 pm Randy Dunlap wrote:
>> On Thu, 22 Apr 2010 18:08:57 -0700 Arve Hjønnevåg wrote:
>> > Add an ioctl, EVIOCSSUSPENDBLOCK, to enable a suspend_blocker that will
>> > block suspend while the event queue is not empty. This allows userspace
>> > code to process input events while the device appears to be asleep.
>>
>> All new ioctls need to be added to Documentation/ioctl/ioctl-number.txt,
>> please.
>
> I do not see the reason for it to be in the kernel still. Have a process
> that listens to all input devices (or subset of them), once events stop
> coming initiate suspend.
>
I think the document added by the first patch explains this. The
solution you propose above will ignore a wakeup key pressed right
after user space decides to initiate suspend.
--
Arve Hjønnevåg
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-24 5:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1271984938-13920-1-git-send-email-arve@android.com>
[not found] ` <1271984938-13920-2-git-send-email-arve@android.com>
[not found] ` <1271984938-13920-3-git-send-email-arve@android.com>
[not found] ` <1271984938-13920-4-git-send-email-arve@android.com>
[not found] ` <1271984938-13920-5-git-send-email-arve@android.com>
[not found] ` <1271984938-13920-6-git-send-email-arve@android.com>
[not found] ` <1271984938-13920-7-git-send-email-arve@android.com>
[not found] ` <1271984938-13920-8-git-send-email-arve@android.com>
2010-04-23 1:08 ` [PATCH 8/9] Input: Block suspend while event queue is not empty Arve Hjønnevåg
2010-04-23 20:56 ` Randy Dunlap
2010-04-23 21:08 ` Dmitry Torokhov
2010-04-24 5:02 ` Arve Hjønnevåg [this message]
2010-04-24 14:36 ` [linux-pm] " Alan Stern
2010-04-25 2:30 ` Rafael J. Wysocki
2010-04-25 15:29 ` Alan Stern
2010-04-25 22:41 ` Arve Hjønnevåg
2010-04-24 4:58 ` Arve Hjønnevåg
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=z2wd6200be21004232202me5d59908y25bf9523fd62edce@mail.gmail.com \
--to=arve@android.com \
--cc=cascardo@holoscopio.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mjg@redhat.com \
--cc=nm127@freemail.hu \
--cc=randy.dunlap@oracle.com \
--cc=rydberg@euromail.se \
--cc=s.neumann@raumfeld.com \
--cc=tero.saarni@gmail.com \
/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).