Searched refs:calling (Results 1 – 25 of 195) sorted by relevance
12345678
| /Zephyr-latest/subsys/rtio/ |
| D | Kconfig | 14 When calling rtio_submit a semaphore is available to sleep the calling
26 When calling rtio_cqe_consume_block a semaphore is available to sleep the
27 calling thread for each completion queue event until the wait count is met.
|
| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | condvar.rst | 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` for
97 one thread or by calling :c:func:`k_condvar_broadcast` for multiple threads.
|
| D | events.rst | 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`.
|
| D | semaphores.rst | 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`.
|
| D | mutexes.rst | 98 It must then be initialized by calling :c:func:`k_mutex_init`.
109 by calling :c:macro:`K_MUTEX_DEFINE`.
120 A mutex is locked by calling :c:func:`k_mutex_lock`.
143 A mutex is unlocked by calling :c:func:`k_mutex_unlock`.
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | lifos.rst | 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 calling
120 A data item is removed from a LIFO by calling :c:func:`k_lifo_get`.
|
| D | fifos.rst | 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 calling
132 A data item is removed from a FIFO by calling :c:func:`k_fifo_get`.
|
| D | stacks.rst | 59 It must then be initialized by calling :c:func:`k_stack_init` or
61 provided and it is instead allocated from the calling thread's resource
77 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`.
|
| D | pipes.rst | 52 byte buffer. The pipe must then be initialized by calling :c:func:`k_pipe_init`.
80 Data is added to a pipe by calling :c:func:`k_pipe_write`.
128 Data is retrieved from the pipe by calling :c:func:`k_pipe_read`.
185 The pipe can be reset by calling :c:func:`k_pipe_reset`. Resetting a pipe
|
| D | message_queues.rst | 74 It must then be initialized by calling :c:func:`k_msgq_init`.
93 by calling :c:macro:`K_MSGQ_DEFINE`.
105 A data item is added to a message queue by calling :c:func:`k_msgq_put`.
136 A data item is taken from a message queue by calling :c:func:`k_msgq_get`.
162 A data item is read from a message queue by calling :c:func:`k_msgq_peek`.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | blob_flash.rst | 14 It must be initialized by calling :c:func:`bt_mesh_blob_flash_rd_init` before being passed to the
22 It must be initialized by calling :c:func:`bt_mesh_blob_flash_rd_init` before being passed to the
|
| D | blob_srv.rst | 68 The BLOB Transfer Server notifies the user of the suspension by calling the :c:member:`suspended
73 Transfer Server notifies the user by calling the :c:member:`resume <bt_mesh_blob_srv_cb.resume>`
81 calling :c:func:`bt_mesh_init`), the BLOB Transfer Server will check for aborted transfers, and call
|
| D | access.rst | 83 and calling :c:func:`bt_mesh_model_send`.
84 * By setting up a :c:struct:`bt_mesh_model_pub` structure and calling
128 Model extensions are done by calling :c:func:`bt_mesh_model_extend` during
143 one user defined data entry per instance by calling
148 storage. The model can retrieve the data by calling the ``read_cb`` passed as
154 data by calling :c:func:`bt_mesh_model_data_store_schedule`. The stack will
191 or more models. A model can extend another model by calling :c:func:`bt_mesh_model_extend`,
192 or correspond to another model by calling :c:func:`bt_mesh_model_correspond`.
|
| /Zephyr-latest/scripts/coccinelle/ |
| D | find_dev_usage.cocci | 25 msg = "ERROR: in {} calling {} param with {}, \
29 msg = "WARNING: in {} calling {} param with {}, \
|
| /Zephyr-latest/soc/nxp/mcx/mcxw/ |
| D | linker.ld | 20 * is done because calling this linker at the beginning will place some sections
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_if.rst | 25 The network interface can be turned ON by calling ``net_if_up()`` and OFF
26 by calling ``net_if_down()``. When the device is powered ON, the network
31 resolved from its index by calling ``net_if_get_by_index()`` and from interface
32 pointer by calling ``net_if_get_by_iface()``.
69 changed by calling :c:func:`net_if_up` or :c:func:`net_if_down` functions.
|
| D | socks5.rst | 28 by calling :c:func:`setsockopt()` like this:
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | fetch_and_get.rst | 14 These functions work together. The fetch APIs block the calling context which
19 :c:struct:`sensor_value` by calling :c:func:`sensor_channel_get` for each channel
23 It should be noted that calling fetch and get from multiple contexts without
|
| /Zephyr-latest/subsys/mgmt/mcumgr/mgmt/ |
| D | Kconfig | 24 Some callbacks support notifying the calling function of a status, in which to accept
25 or decline the current operation, by returning false this will signal to the calling
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | slabs.rst | 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`.
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | tmap.rst | 13 calling :code:`tmap init`.
|
| /Zephyr-latest/cmake/bintools/ |
| D | bintools_template.cmake | 56 # memusage_flag : Flags that must always be applied when calling memusage command
59 # memusage_byproducts : Byproducts (files) generated when calling memusage
65 # elfconvert_flag : Flags that must always be applied when calling elfconvert comma…
86 # disassembly_flag : Flags that must always be applied when calling disassembly com…
97 # readelf_flag : Flags that must always be applied when calling readelf command
107 # strip_flag : Flags that must always be applied when calling strip command
|
| /Zephyr-latest/drivers/sensor/nuvoton/nuvoton_adc_cmp_npcx/ |
| D | Kconfig | 21 Threshold detection ISR utilizes system work queue for calling
|
| /Zephyr-latest/samples/userspace/syscall_perf/ |
| D | README.rst | 22 instructions executed while calling :c:func:`k_current_get()`.
|
| /Zephyr-latest/tests/ztest/fail/ |
| D | README.rst | 12 binary which is expected to fail by calling one of the following:
|
12345678
