Lines Matching refs:will
56 For example: :c:func:`k_ms_to_ticks_ceil32` will convert a
59 :c:func:`k_cyc_to_us_floor64` will convert a measured cycle count
88 Conceptually, this indicates the time at which an event will occur.
93 routine will return with an error code if no data is available.
99 indicating when a work queue item will be added to the system queue.
112 time" will already have advanced. This is to ensure that timers scheduled from
113 within another timer's callback will always be calculated with a precise offset
123 :c:macro:`K_CYC()` specify timeout values that will expire after specified
127 being 32 bits. Large uptime counts in non-tick units will experience
129 timing-sensitive applications with long uptimes will be configured to
134 indicates a timeout that will expire after the system uptime reaches
185 must be correct) but delay after that will cause events to be
209 tick will be announced regardless of timeout status.
220 a multiprocessor context. The kernel will internally synchronize all
232 simultaneously, that only one will provide the current tick count to
244 So by default, every CPU will see simultaneous timer interrupts for
248 minimizes the chance that an errant ISR or interrupt lock will delay
271 In general, code like this will port just like applications code will.
285 will need to use a different, integer-valued token to represent
330 an uptime tick at which it will expire. So such a loop might look like: