Lines Matching +full:wakeup +full:- +full:delay +full:- +full:ms

2 delays - Information on the various kernel delay / sleep mechanisms
6 RightWay (TM) to insert a delay?"
14 ----------------
18 it really need to delay in atomic context?" If so...
21 	You must use the `*delay` family of functions. These
24 	the desired delay:
30 	udelay is the generally preferred API; ndelay-level
31 	precision may not actually exist on many non-PC devices.
38 NON-ATOMIC CONTEXT:
45 	-- Backed by busy-wait loop:
49 	-- Backed by hrtimers:
53 	-- Backed by jiffies / legacy_timers
58 	Unlike the `*delay` family, the underlying mechanism
66 		- Why not usleep?
67 			On slower systems, (embedded, OR perhaps a speed-
73 	SLEEPING FOR ~USECS OR SMALL MSECS ( 10us - 20ms):
76 		- Why not msleep for (1ms - 20ms)?
81 			will often sleep longer (~20 ms actual sleep for any
82 			value given in the 1~20ms range). In many cases this
85 		- Why is there no "usleep" / What is a good range?
87 			wakeup will be very precise (ish), thus a simple
92 			free to coalesce your wakeup with any other wakeup
99 			delay / performance for your specific code path. Exact
103 	SLEEPING FOR LARGER MSECS ( 10ms+ )
106 		- What's the difference?
114 	FLEXIBLE SLEEPING (any delay, uninterruptible)