Home
last modified time | relevance | path

Searched refs:condition (Results 1 – 25 of 52) sorted by relevance

123

/Zephyr-Core-3.4.0/doc/kernel/services/synchronization/
Dcondvar.rst6 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.
32 the condition using :c:func:`k_condvar_signal` or
[all …]
/Zephyr-Core-3.4.0/samples/bluetooth/peripheral_esp/src/
Dmain.c79 uint8_t condition; member
99 .condition = ESS_VALUE_CHANGED,
111 .condition = ESS_VALUE_CHANGED,
174 uint8_t condition; member
179 uint8_t condition; member
190 switch (sensor->condition) { in read_temp_trigger_setting()
196 &sensor->condition, in read_temp_trigger_setting()
197 sizeof(sensor->condition)); in read_temp_trigger_setting()
204 rp.condition = sensor->condition; in read_temp_trigger_setting()
214 rp.condition = sensor->condition; in read_temp_trigger_setting()
[all …]
/Zephyr-Core-3.4.0/samples/kernel/condition_variables/condvar/
DREADME.rst9 This sample demonstrates the usage of condition variables in a
12 thread. A thread uses a condition variable to wait for a condition to
15 pending on the condition variable. The sample can be used with any
/Zephyr-Core-3.4.0/drivers/ieee802154/
Dieee802154_cc13xx_cc26xx_subg.c91 .condition.rule = COND_NEVER,
163 .condition.rule = COND_NEVER,
353 drv_data->cmd_prop_cs.condition.rule = COND_NEVER; in ieee802154_cc13xx_cc26xx_subg_cca()
503 drv_data->cmd_prop_cs.condition.rule = COND_STOP_ON_TRUE; in ieee802154_cc13xx_cc26xx_subg_tx()
809 drv_data->cmd_fs.condition.rule = COND_NEVER; in ieee802154_cc13xx_cc26xx_subg_init()
838 .condition.rule = COND_NEVER,
843 .condition.rule = COND_NEVER,
874 .condition.rule = COND_NEVER,
890 .condition.rule = COND_NEVER,
Dieee802154_cc13xx_cc26xx.c344 drv_data->cmd_ieee_tx.condition.rule = in ieee802154_cc13xx_cc26xx_tx()
621 drv_data->cmd_fs.condition.rule = COND_NEVER; in ieee802154_cc13xx_cc26xx_init()
655 .condition.rule = COND_NEVER,
732 .condition.rule = COND_STOP_ON_FALSE,
757 .condition.rule = COND_NEVER,
775 .condition.rule = COND_NEVER,
791 .condition.rule = COND_NEVER,
/Zephyr-Core-3.4.0/doc/connectivity/networking/api/
Dnet_pkt_filter.rst26 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-Core-3.4.0/doc/services/device_mgmt/smp_groups/
Dsmp_group_0.rst109 | | only appears if non-zero (error condition). |
204 | | only appears if non-zero (error condition). |
288 | | only appears if non-zero (error condition). |
361 | | only appears if non-zero (error condition). |
432 | | only appears if non-zero (error condition). |
511 | | only appears if non-zero (error condition). |
578 | | only appears if non-zero (error condition). |
670 | | only appears if non-zero (error condition). |
Dsmp_group_2.rst112 | | only appears if non-zero (error condition). |
183 | | only appears if non-zero (error condition). |
Dsmp_group_8.rst137 | | only appears if non-zero (error condition). |
257 | | only appears if non-zero (error condition). |
336 | | only appears if non-zero (error condition). |
457 | | only appears if non-zero (error condition). |
602 | | only appears if non-zero (error condition). |
Dsmp_group_9.rst104 | | only appears if non-zero (error condition). |
Dsmp_group_1.rst191 | | only appears if non-zero (error condition). |
377 | | appears if non-zero (error condition). |
461 | | only appears if non-zero (error condition). |
/Zephyr-Core-3.4.0/soc/riscv/riscv-privileged/andes_v5/
DKconfig.defconfig.series6 # Kconfig picks the first default with a satisfied condition.
/Zephyr-Core-3.4.0/doc/kernel/services/
Dpolling.rst30 **poll events**, one for each condition.
34 Each event must specify which **type** of condition must be satisfied so that
35 its state is changed to signal the requested condition has been met.
37 Each event must specify what **kernel object** it wants the condition to be
40 Each event must specify which **mode** of operation is used when the condition
72 event a call to :c:func:`k_poll` will wait for its condition to be
123 :c:macro:`K_FOREVER` to either not wait or wait until an event condition is
/Zephyr-Core-3.4.0/samples/kernel/condition_variables/simple/
DREADME.rst9 This sample demonstrates the usage of condition variables in a
12 thread. Main thread uses a condition variable to wait for a condition to
15 pending on the condition variable. The sample can be used with any
/Zephyr-Core-3.4.0/lib/posix/
DKconfig27 the pthread mutex, condition variable and barrier IPC
57 int "Maximum simultaneously active condition variables in a POSIX application"
61 Maximum number of simultaneously active condition variables in a POSIX application.
/Zephyr-Core-3.4.0/tests/posix/pthread_pressure/
DKconfig24 If there is a race condition, a value of zero here should
/Zephyr-Core-3.4.0/tests/drivers/sdhc/
DREADME.txt21 * Request test: Make a request to read the card interface condition,
/Zephyr-Core-3.4.0/subsys/debug/
DKconfig303 bool "Disable condition info for asserts"
305 This option removes the assert condition from the printed assert
307 necessary for tiny targets. It is recommended to disable condition
308 info before disabling file info since the condition can be found in
325 condition is false. The tests that validate the assert feature may
Dgdbstub.c602 #define CHECK_ERROR(condition) \ in z_gdb_main_loop() argument
604 if ((condition)) { \ in z_gdb_main_loop()
/Zephyr-Core-3.4.0/doc/kernel/services/other/
Dfatal.rst159 :c:func:`k_oops()`. This should be used to indicate an unrecoverable condition
171 encounters a panic condition, as the entire system needs to be reset.
209 should be treated as a very serious condition impacting the health of the
/Zephyr-Core-3.4.0/boards/posix/doc/
Darch_soc.rst113 Similarly the following code where we expect ``condition`` to be
119 volatile condition = true;
120 while (condition){}
165 volatile condition = true;
166 while (condition) {
/Zephyr-Core-3.4.0/subsys/usb/device_next/class/
Dusbd_msc_scsi.c196 #define GET_POWER_CONDITION_MODIFIER(cmd) (cmd->condition & BIT_MASK(4))
216 uint8_t condition; in SCSI_CMD_STRUCT() local
/Zephyr-Core-3.4.0/scripts/
Dcheckpatch.pl1502 my $condition = substr($blk, $soff, $coff - $soff + 1);
1509 return ($statement, $condition,
1558 my ($statement, $condition, $level);
1563 ($statement, $condition, $linenr, $remain, $off, $level) =
1566 push(@chunks, [ $condition, $statement ]);
1567 if (!($remain > 0 && $condition =~ /^\s*(?:\n[+-])?\s*(?:if|else|do)\b/s)) {
1574 ($statement, $condition, $linenr, $remain, $off, $level) =
1577 last if (!($remain > 0 && $condition =~ /^(?:\s*\n[+-])*\s*(?:else|do)\b/s));
1579 push(@chunks, [ $condition, $statement ]);
/Zephyr-Core-3.4.0/doc/build/kconfig/
Dsetting.rst242 uses the first ``default`` with a satisfied condition, where an empty condition
/Zephyr-Core-3.4.0/scripts/ci/
Dpylintrc84 len-as-condition,

123