Searched full:calling (Results 1 – 25 of 563) sorted by relevance
12345678910>>...23
14 When calling rtio_submit a semaphore is available to sleep the calling26 When calling rtio_cqe_consume_block a semaphore is available to sleep the27 calling thread for each completion queue event until the wait count is met.
45 * credentials_lock before calling this function.53 * credentials_lock before calling this function.73 * calling, and will be set to the amount written to the destination buffer after calling77 * credentials_lock before calling this function.
33 allocated from the calling thread's resource pool.72 It must then be initialized by calling :c:func:`k_fifo_init`.83 by calling :c:macro:`K_FIFO_DEFINE`.94 A data item is added to a FIFO by calling :c:func:`k_fifo_put`.122 by calling :c:func:`k_fifo_put_list` or :c:func:`k_fifo_put_slist`.126 the data item, instead additional memory will be allocated from the calling132 A data item is removed from a FIFO by calling :c:func:`k_fifo_get`.
33 allocated from the calling thread's resource pool.63 It must then be initialized by calling :c:func:`k_lifo_init`.74 by calling :c:macro:`K_LIFO_DEFINE`.85 A data item is added to a LIFO by calling :c:func:`k_lifo_put`.114 the data item, instead additional memory will be allocated from the calling120 A data item is removed from a LIFO by calling :c:func:`k_lifo_get`.
59 It must then be initialized by calling :c:func:`k_stack_init` or61 provided and it is instead allocated from the calling thread's resource77 by calling :c:macro:`K_STACK_DEFINE`.89 A data item is added to a stack by calling :c:func:`k_stack_push`.112 A data item is taken from a stack by calling :c:func:`k_stack_pop`.
66 initialized by calling :c:func:`k_pipe_init`.80 calling :c:macro:`K_PIPE_DEFINE`.92 Data is added to a pipe by calling :c:func:`k_pipe_put`.138 Data is read from the pipe by calling :c:func:`k_pipe_get`.178 Data is flushed from the pipe's ring buffer by calling199 All data in the pipe is flushed by calling :c:func:`k_pipe_flush`.
16 - "Calling huge body of code that doesn't fit in memory"18 - "Calling it a second time"
41 Calling huge body of code that doesn't fit in memory43 Calling it a second time
48 It must then be initialized by calling :c:func:`k_condvar_init`.59 by calling :c:macro:`K_CONDVAR_DEFINE`.70 A thread can wait on a condition by calling :c:func:`k_condvar_wait`.96 A condition variable is signaled on by calling :c:func:`k_condvar_signal` for97 one thread or by calling :c:func:`k_condvar_broadcast` for multiple threads.
52 It must then be initialized by calling :c:func:`k_event_init`.63 by calling :c:macro:`K_EVENT_DEFINE`.74 Events in an event object are set by calling :c:func:`k_event_set`.93 Events are posted to an event object by calling :c:func:`k_event_post`.114 Threads wait for events by calling :c:func:`k_event_wait`.
58 It must then be initialized by calling :c:func:`k_sem_init`.70 by calling :c:macro:`K_SEM_DEFINE`.81 A semaphore is given by calling :c:func:`k_sem_give`.99 A semaphore is taken by calling :c:func:`k_sem_take`.
14 * The system will be transitioning out of sleep when calling this function.22 * The system will transition to sleep after calling this function.
49 * parameters). This function must be called after calling CANopenNode64 * saved by the application by periodically calling @ref104 * called after calling CANopenNode `CO_init()`.153 * It can be used to e.g. wake the loop polling calling CO_process.163 * This can be used to wake the loop calling CO_process when an incoming
25 The network interface can be turned ON by calling ``net_if_up()`` and OFF26 by calling ``net_if_down()``. When the device is powered ON, the network31 resolved from its index by calling ``net_if_get_by_index()`` and from interface32 pointer by calling ``net_if_get_by_iface()``.69 changed by calling :c:func:`net_if_up` or :c:func:`net_if_down` functions.
14 These functions work together. The fetch APIs block the calling context which19 :c:struct:`sensor_value` by calling :c:func:`sensor_channel_get` for each channel23 It should be noted that calling fetch and get from multiple contexts without
14 It must be initialized by calling :c:func:`bt_mesh_blob_flash_rd_init` before being passed to the22 It must be initialized by calling :c:func:`bt_mesh_blob_flash_rd_init` before being passed to the
74 * To be populated by the app before calling hash_begin_session().76 * by calling crypto_query_hwcaps().86 * be filled up by the app before calling hash_compute().
118 /** To be populated by the app before calling begin_session() */149 * in a session. To be populated by the app before calling159 * before calling begin_session()165 * To be populated by the app before calling begin_session().167 * by calling crypto_query_hwcaps().
24 Some callbacks support notifying the calling function of a status, in which to accept25 or decline the current operation, by returning false this will signal to the calling
24 * only one callback may be installed at a time. Calling this a second time37 * Calling this function simulates that data was sent from the host to the DUT.
56 # memusage_flag : Flags that must always be applied when calling memusage command59 # memusage_byproducts : Byproducts (files) generated when calling memusage65 # elfconvert_flag : Flags that must always be applied when calling elfconvert comma…85 # disassembly_flag : Flags that must always be applied when calling disassembly com…96 # readelf_flag : Flags that must always be applied when calling readelf command106 # strip_flag : Flags that must always be applied when calling strip command
33 * @brief Power down the calling core47 * into the calling supervisory software or have been previously powered down
19 # 2. Tx devices pushes all created advs to the pool by calling `bt_mesh_adv_send` function21 # a work item which suspends the advertiser by calling `bt_mesh_adv_disable`.
71 It must then be initialized by calling :c:func:`k_mem_slab_init`.84 by calling :c:macro:`K_MEM_SLAB_DEFINE`.102 A memory block is allocated by calling :c:func:`k_mem_slab_alloc`.122 A memory block is released by calling :c:func:`k_mem_slab_free`.
14 description: The method of calling the OP-TEE Trusted OS.
