Lines Matching refs:func
54 Using the return values of :c:func:`k_work_busy_get()` or
55 :c:func:`k_work_is_pending()`, or measurements of remaining time until
93 * marked canceling (because a thread used :c:func:`k_work_cancel_sync()` to
99 (:c:func:`k_work_is_pending()`) or **busy** (:c:func:`k_work_busy_get()`).
169 The :c:func:`k_work_poll_submit` interface schedules a triggered work
173 In contrast to :c:func:`k_poll`, the triggered work does not require
227 memory or calling :c:func:`k_work_queue_init`, and then calling
228 :c:func:`k_work_queue_start`. The stack area must be defined using
251 :c:func:`k_work_queue_start()` for details.
255 * :c:func:`k_work_queue_drain()` can be used to block the caller until the
264 * :c:func:`k_work_queue_unplug()` removes any previous block on submission to
271 be initialized by calling :c:func:`k_work_init`, unless it is defined using
276 calling :c:func:`k_work_submit`, or to a specified workqueue by
277 calling :c:func:`k_work_submit_to_queue`.
320 * :c:func:`k_work_busy_get()` returns a snapshot of flags indicating work item
324 * :c:func:`k_work_is_pending()` is a helper that indicates ``true`` if and only
326 * :c:func:`k_work_flush()` may be invoked from threads to block until the work
328 * :c:func:`k_work_cancel()` attempts to prevent the work item from being
331 * :c:func:`k_work_cancel_sync()` may be invoked from threads to block until
334 can be used after :c:func:`k_work_cancel()` is invoked (from an ISR)` to
342 :c:func:`k_work_init_delayable`.
349 * :c:func:`k_work_schedule()` (or :c:func:`k_work_schedule_for_queue()`)
355 * :c:func:`k_work_reschedule()` (or :c:func:`k_work_reschedule_for_queue()`)
364 minimal timeout (unless :c:func:`k_work_schedule()` is used and a previous
370 The helper function :c:func:`k_work_delayable_from_work()` can be used to get
377 * :c:func:`k_work_delayable_busy_get()` is the analog to :c:func:`k_work_busy_get()`
379 * :c:func:`k_work_delayable_is_pending()` is the analog to
380 :c:func:`k_work_is_pending()` for delayable work.
381 * :c:func:`k_work_flush_delayable()` is the analog to :c:func:`k_work_flush()`
383 * :c:func:`k_work_cancel_delayable()` is the analog to
384 :c:func:`k_work_cancel()` for delayable work; similarly with
385 :c:func:`k_work_cancel_delayable_sync()`.
391 from any context using :c:func:`k_work_busy_get()` and
392 :c:func:`k_work_delayable_busy_get()` some use cases require synchronizing
393 with work items after they've been submitted. :c:func:`k_work_flush()`,
394 :c:func:`k_work_cancel_sync()`, and :c:func:`k_work_cancel_delayable_sync()`
473 * Submitting a work item (:c:func:`k_work_submit_to_queue`) can fail if the
477 * Asynchronous cancellation (:c:func:`k_work_cancel` or
478 :c:func:`k_work_cancel_delayable`) can complete while the work item is still
510 state with :c:func:`k_work_is_pending` or :c:func:`k_work_busy_get`, or
512 :c:func:`k_work_delayable_remaining_get()`. Those checks are fragile: a "busy"
525 A rare case where you could safely use :c:func:`k_work_is_pending` is as a
526 check to avoid invoking :c:func:`k_work_flush` or
527 :c:func:`k_work_cancel_sync`, if you are *certain* that nothing else might