On Saturday 24 April 2010, Alan Stern wrote: > On Fri, 23 Apr 2010, Arve Hjønnevåg wrote: > > > On Fri, Apr 23, 2010 at 2:08 PM, Dmitry Torokhov > > <dmitry.torokhov@xxxxxxxxx> 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. This solution is not practical with the Android user space AFAICT. > > 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. > > Is there some reason why this feature needs to be enabled by an > ioctl? Why not make this suspend blocker permanently enabled? The ioctl is there so that user space can use suspend blockers, which is needed because only user space know that some activities are going to continue and therefore the system should not be suspended (like playing music "in the background"). >From all of the interfaces that could be used for this purpose ioctl appears to be the most convenient (we need something that is per process and allows us to carry out four operations: creat, destroy, activate, deactivate). Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
