| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | condvar.rst | 3 Condition Variables
6 A :dfn:`condition variable` is a synchronization primitive
7 that enables threads to wait until a particular condition occurs.
16 Any number of condition variables can be defined (limited only by available RAM). Each
17 condition variable is referenced by its memory address.
19 To wait for a condition to become true, a thread can make use of a condition
22 A condition variable is basically a queue of threads that threads can put
23 themselves on when some state of execution (i.e., some condition) is not as
24 desired (by waiting on the condition). The function
28 #. Puts the current thread in the condition variable queue.
[all …]
|
| /Zephyr-latest/modules/hal_nordic/nrf_802154/include/ |
| D | nrf_802154_assert_zephyr.h | 14 #define NRF_802154_ASSERT(condition) __ASSERT_NO_MSG(condition) argument
20 #define NRF_802154_ASSERT(condition) \ argument
22 if (!(condition)) { \
|
| /Zephyr-latest/include/zephyr/net/ |
| D | net_pkt_filter.h | 46 npf_test_fn_t *fn; /**< packet condition test function */
193 * the fate of the packet. If one condition is false then the next rule in
235 * @brief Statically define an "interface match" packet filter condition
237 * @param _name Name of the condition
247 * @brief Statically define an "interface unmatch" packet filter condition
249 * @param _name Name of the condition
259 * @brief Statically define an "orig interface match" packet filter condition
261 * @param _name Name of the condition
271 * @brief Statically define an "orig interface unmatch" packet filter condition
273 * @param _name Name of the condition
[all …]
|
| /Zephyr-latest/samples/kernel/condition_variables/condvar/ |
| D | README.rst | 2 :name: Condition Variables
5 Manipulate condition variables in a multithreaded application.
10 This sample demonstrates the usage of :ref:`condition variables <condvar>` in a
11 multithreaded application. Condition variables are used with a mutex
13 thread. A thread uses a condition variable to wait for a condition to
16 pending on the condition variable. The sample can be used with any
54 watch_count: thread 1 Condition signal received. Count= 12
|
| /Zephyr-latest/samples/bluetooth/peripheral_esp/src/ |
| D | main.c | 124 /* ES trigger setting - Value Notification condition */
125 uint8_t condition; member
145 .condition = ESS_TRIGGER_VALUE_CHANGED,
157 .condition = ESS_TRIGGER_VALUE_CHANGED,
220 uint8_t condition; member
225 uint8_t condition; member
236 switch (sensor->condition) { in read_temp_trigger_setting()
242 &sensor->condition, in read_temp_trigger_setting()
243 sizeof(sensor->condition)); in read_temp_trigger_setting()
250 rp.condition = sensor->condition; in read_temp_trigger_setting()
[all …]
|
| /Zephyr-latest/include/zephyr/drivers/interrupt_controller/ |
| D | wuc_ite_it8xxx2.h | 14 * @brief A trigger condition on the corresponding input generates
23 * @brief A trigger condition on the corresponding input doesn't
32 * @brief Write-1-clear a trigger condition that occurs on the
|
| D | sam0_eic.h | 17 * @brief EIC trigger condition
42 * @param trigger trigger condition
|
| /Zephyr-latest/drivers/i2c/ |
| D | i2c_bitbang.c | 208 /* We want an initial Start condition */ in i2c_bitbang_transfer()
224 /* Start condition? */ in i2c_bitbang_transfer()
234 /* Send address after any Start condition */ in i2c_bitbang_transfer()
287 * a START condition followed by 9 STOP conditions. in i2c_bitbang_recover_bus()
290 * issuing a START condition followed by 9 SCL clock pulses in i2c_bitbang_recover_bus()
291 * with SDA held high/floating, a REPEATED START condition, in i2c_bitbang_recover_bus()
292 * and a STOP condition. in i2c_bitbang_recover_bus()
297 /* Start condition */ in i2c_bitbang_recover_bus()
305 /* Another start condition followed by a stop condition */ in i2c_bitbang_recover_bus()
|
| /Zephyr-latest/tests/posix/common/src/ |
| D | cond.c | 12 * @brief Test to demonstrate limited condition variable resources
36 * @brief Test to that there are no condition variable resource leaks
38 * @details Demonstrate that condition variables may be used over and over again.
|
| /Zephyr-latest/dts/bindings/sensor/ |
| D | espressif,esp32-pcnt.yaml | 119 0 (Default) - Inhibit counter (counter value will not change in this condition).
132 0 (Default) - Inhibit counter (counter value will not change in this condition).
147 2 - Control mode: Inhibit counter (counter value will not change in this condition).
160 2 - Control mode: Inhibit counter (counter value will not change in this condition).
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_pkt_filter.rst | 26 condition is false then the next rule in the list is considered.
44 can be embedded into a larger structure when a specific condition requires
49 to statically define condition instances for various conditions, and
|
| /Zephyr-latest/tests/bluetooth/host/id/bt_id_add/src/ |
| D | main.c | 74 * - 'bt_dev.le.rl_entries > bt_dev.le.rl_size' condition is true
102 * - 'bt_dev.le.rl_entries > bt_dev.le.rl_size' condition is false
114 /* Break the host-side resolving condition */ in ZTEST()
152 * - 'bt_dev.le.rl_entries > bt_dev.le.rl_size' condition is false
168 /* Break the host-side resolving condition */ in ZTEST()
213 /* Break the host-side resolving condition */ in ZTEST()
262 /* Break the host-side resolving condition */ in ZTEST()
316 /* Break the host-side resolving condition */ in ZTEST()
|
| /Zephyr-latest/dts/bindings/rtc/ |
| D | nxp,pcf8523.yaml | 53 - standard: The power failure condition happens when VDD < VBAT and VDD < Vth(sw)bat
54 - direct: The power failure condition happens when VDD < VBAT
|
| /Zephyr-latest/tests/net/lib/coap_client/src/ |
| D | stubs.h | 27 /** zsock_poll: Poll for exceptional condition */
31 /** zsock_poll: Poll results in error condition (output value only) */
|
| /Zephyr-latest/samples/drivers/soc_flash_nrf/src/ |
| D | main.c | 42 * Depending on value of condition erase a device or not. The condition
46 static void erase_when_needed(const struct device *dev, bool condition, in erase_when_needed() argument
52 * always check condition if there are both kind of devices. in erase_when_needed()
54 if (FLASH_PE_RUNTIME_CHECK(condition)) { in erase_when_needed()
61 (void)condition; in erase_when_needed()
|
| /Zephyr-latest/tests/bluetooth/host/id/bt_id_del/src/ |
| D | main.c | 108 * - 'bt_dev.le.rl_entries > bt_dev.le.rl_size + 1' condition is false
120 /* Break the host-side resolving condition */ in ZTEST()
158 * - 'bt_dev.le.rl_entries > bt_dev.le.rl_size + 1' condition is false
174 /* Break the host-side resolving condition */ in ZTEST()
222 /* Break the host-side resolving condition */ in ZTEST()
274 /* Break the host-side resolving condition */ in ZTEST()
324 /* Break the host-side resolving condition */ in ZTEST()
378 /* Break the host-side resolving condition */ in ZTEST()
|
| /Zephyr-latest/subsys/testsuite/ztest/include/zephyr/ |
| D | ztest_assert.h | 166 * instead use zassert_{condition} macros below.
172 * @param cond Condition to check
200 * instead use zassume_{condition} macros below.
210 * @param cond Condition to check
238 * instead use zexpect_{condition} macros below.
240 * @param cond Condition to check
272 * @param cond Condition to check
279 * @param cond Condition to check
286 * @param cond Condition to check
293 * @param cond Condition to check
[all …]
|
| /Zephyr-latest/tests/benchmarks/latency_measure/src/ |
| D | condvar.c | 8 * @file measure time for various condition variable operations
9 * 1. Block waiting for a condition variable
10 * 2. Signal a condition variable (with context switch)
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.pthread | 10 Select 'y' here to enable POSIX threads, mutexes, condition variables, and thread-specific
34 int "Maximum number of POSIX condition variables"
37 Maximum simultaneously active condition variables in a POSIX application.
179 module-str = POSIX condition variable
|
| /Zephyr-latest/samples/kernel/condition_variables/simple/ |
| D | README.rst | 5 Condition Variables
11 This sample demonstrates the usage of condition variables in a
12 multithreaded application. Condition variables are used with a mutex
14 thread. Main thread uses a condition variable to wait for a condition to
17 pending on the condition variable. The sample can be used with any
|
| /Zephyr-latest/doc/kernel/services/ |
| D | polling.rst | 32 **poll events**, one for each condition.
36 Each event must specify which **type** of condition must be satisfied so that
37 its state is changed to signal the requested condition has been met.
39 Each event must specify what **kernel object** it wants the condition to be
42 Each event must specify which **mode** of operation is used when the condition
74 event a call to :c:func:`k_poll` will wait for its condition to be
142 :c:macro:`K_FOREVER` to either not wait or wait until an event condition is
|
| /Zephyr-latest/include/zephyr/drivers/i3c/ |
| D | target_device.h | 123 * a start condition for a write operation to the address associated
163 * start condition for a read operation from the address associated
169 * bus operations until a new start condition is received.
192 * bus operations until a new start condition is received.
230 * a new start condition is received.
249 * @brief Function called when a stop condition is observed after a
250 * start condition addressed to a particular device.
|
| /Zephyr-latest/drivers/interrupt_controller/ |
| D | Kconfig.npcx | 19 Workaround the issue "MIWU Any Edge Trigger Condition"
|
| /Zephyr-latest/soc/andestech/ae350/ |
| D | Kconfig.defconfig | 6 # Kconfig picks the first default with a satisfied condition.
|
| /Zephyr-latest/cmake/linker/lld/ |
| D | linker_libraries.cmake | 11 # When new link principle is fully introduced, then the below condition can
|
