Lines Matching +full:extra +full:- +full:wait +full:- +full:time

6 The polling API is used to wait concurrently for any one of multiple conditions
20 The polling API allows a single thread to wait concurrently for one or more
25 - a semaphore becomes available
26 - a kernel FIFO contains data ready to be retrieved
27 - a kernel message queue contains data ready to be retrieved
28 - a kernel pipe contains data ready to be retrieved
29 - a poll signal is raised
31 A thread that wants to wait on multiple conditions must define an array of
48 Apart from the kernel objects, there is also a **poll signal** pseudo-object
54 :c:func:`k_poll` was called, or due to the preemptive multi-threading
74 event a call to :c:func:`k_poll` will wait for its condition to be
91 .. code-block:: c
110 .. code-block:: c
140 :c:func:`k_poll`. A timeout can be specified to wait only for a specified
141 amount of time, or the special values :c:macro:`K_NO_WAIT` and
142 :c:macro:`K_FOREVER` to either not wait or wait until an event condition is
146 can wait in it as the app wants.
147 Notice that the waiters will be served in first-come-first-serve order,
151 -:c:macro:`EAGAIN`.
153 .. code-block:: c
156     // -EADDRINUSE will not occur; the semaphore and/or data will be available
182 .. code-block:: c
215 one thread can wait for.
222 .. code-block:: c
232 pass extra information to the thread waiting on the event.
234 .. code-block:: c
256             // A-OK!
273 .. code-block:: c
294                 // A-OK!
308 possible that by the time the application checks, the event state may
313 FIFOs are more error-proof in this sense because they can't "miss"