[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <z2wd6200be21004232202me5d59908y25bf9523fd62edce@mail.gmail.com>
Date: Fri, 23 Apr 2010 22:02:50 -0700
From: Arve Hjønnevåg <arve@...roid.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Randy Dunlap <randy.dunlap@...cle.com>,
linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
Thadeu Lima de Souza Cascardo <cascardo@...oscopio.com>,
Márton Németh <nm127@...email.hu>,
Sven Neumann <s.neumann@...mfeld.com>,
Tero Saarni <tero.saarni@...il.com>,
Henrik Rydberg <rydberg@...omail.se>,
Matthew Garrett <mjg@...hat.com>,
Jiri Kosina <jkosina@...e.cz>, linux-input@...r.kernel.org
Subject: Re: [PATCH 8/9] Input: Block suspend while event queue is not empty.
On Fri, Apr 23, 2010 at 2:08 PM, Dmitry Torokhov
<dmitry.torokhov@...il.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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists