From d3695ae2c75314b8cb043d35e2aad6085e4403c8 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Mon, 7 Jul 2014 07:39:41 +0200 Subject: epoll.7: Minor tweaks to Neil Brown's patch Signed-off-by: Michael Kerrisk --- man7/epoll.7 | 28 +++++++++++++++------------- 1 file changed, 15 insertions(+), 13 deletions(-) diff --git a/man7/epoll.7 b/man7/epoll.7 index 31b1a8c8c..2768d4912 100644 --- a/man7/epoll.7 +++ b/man7/epoll.7 @@ -179,28 +179,30 @@ If the system is in mode via .I /sys/power/autosleep and an event happens which wakes the device from sleep, the device -driver will only keep the device awake until that event is queued. To -keep the device awake until the event has been processed it is -necessary to use -.B epoll -and the +driver will only keep the device awake until that event is queued. +To keep the device awake until the event has been processed, +it is necessary to use the +.BR epoll (7) .B EPOLLWAKEUP flag. -When this flag is set in the +When the +.B EPOLLWAKEUP +flag is set in the .B events field for a -.I struct epoll_event -then system will be kept awake from the moment the event is queued, +.IR "struct epoll_event" , +the system will be kept awake from the moment the event is queued, through the -.IR epoll_wait (2) +.BR epoll_wait (2) call which returns the event until the subsequent -.IR epoll_wait (2) -call. If the event should keep the system awake beyond that time, -the a separate +.BR epoll_wait (2) +call. +If the event should keep the system awake beyond that time, +then a separate .I wake_lock should be taken before the second -.IR epoll_wait (2) +.BR epoll_wait (2) call. .SS /proc interfaces The following interfaces can be used to limit the amount of -- cgit v1.2.3