Searched refs:loop (Results 51 – 75 of 114) sorted by relevance
12345
/Zephyr-latest/scripts/kconfig/ |
D | kconfiglib.py | 6653 loop = _check_dep_loop_choice(dep, None) \ 6657 if loop: 6659 return _found_dep_loop(loop, sym) 6662 loop = _check_dep_loop_choice(sym.choice, sym) 6663 if loop: 6665 return _found_dep_loop(loop, sym) 6696 loop = _check_dep_loop_sym(sym, True) 6697 if loop: 6699 return _found_dep_loop(loop, choice) 6717 def _found_dep_loop(loop, cur): argument [all …]
|
/Zephyr-latest/doc/kernel/services/threads/ |
D | system_threads.rst | 34 loop. The idle thread remains in existence as long as the system is running
|
/Zephyr-latest/boards/native/doc/ |
D | arch_soc.rst | 105 will stall the execution. For example, the following busy wait loop code, 147 If a busy wait loop exists, it will become evident as the application will be 148 stalled in it. To find the loop, you can run the binary in a debugger and 150 some part of that loop. 152 The best solution is to remove that busy wait loop, and instead use 157 If removing the busy loop is really not an option, you may add a conditionally
|
/Zephyr-latest/modules/segger/ |
D | Kconfig | 78 bool "Use a simple byte-loop instead of standard memcpy"
|
/Zephyr-latest/doc/services/storage/nvs/ |
D | nvs.rst | 47 endless loop of flash page erases when there is limited free space. When such 48 a loop is detected NVS returns that there is no more space available.
|
/Zephyr-latest/doc/kernel/services/ |
D | polling.rst | 179 When :c:func:`k_poll` is called in a loop, the events state must be reset 268 If the signal is to be polled in a loop, *both* its event state must be 311 signal only from within the thread invoking the :c:func:`k_poll` loop, or else
|
/Zephyr-latest/samples/subsys/fs/zms/ |
D | README.rst | 20 A loop is executed where we mount the storage system, and then write all set
|
/Zephyr-latest/ |
D | .ruff-excludes.toml | 58 "B007", # https://docs.astral.sh/ruff/rules/unused-loop-control-variable 68 "B007", # https://docs.astral.sh/ruff/rules/unused-loop-control-variable 69 "B020", # https://docs.astral.sh/ruff/rules/loop-variable-overrides-iterator 77 "B007", # https://docs.astral.sh/ruff/rules/unused-loop-control-variable 82 "B007", # https://docs.astral.sh/ruff/rules/unused-loop-control-variable 91 "B007", # https://docs.astral.sh/ruff/rules/unused-loop-control-variable 99 "B007", # https://docs.astral.sh/ruff/rules/unused-loop-control-variable 106 "B007", # https://docs.astral.sh/ruff/rules/unused-loop-control-variable 118 "B007", # https://docs.astral.sh/ruff/rules/unused-loop-control-variable 124 "B007", # https://docs.astral.sh/ruff/rules/unused-loop-control-variable [all …]
|
/Zephyr-latest/samples/basic/button/ |
D | README.rst | 112 iteration of the main loop, the state of GPIO line is monitored and printed to
|
/Zephyr-latest/share/zephyr-package/cmake/ |
D | zephyr_package_search.cmake | 109 # Current Zephyr is preferred one, let's just break the loop and continue processing.
|
/Zephyr-latest/tests/kernel/context/ |
D | README.txt | 44 - Continuation irq_lock: unlock interrupts, loop and verify the tick
|
/Zephyr-latest/samples/userspace/prod_consumer/ |
D | README.rst | 34 The control loop is as follows:
|
/Zephyr-latest/doc/hardware/peripherals/sensor/ |
D | read_and_decode.rst | 46 entirely out of the loop in handling sensor events like FIFO watermarks.
|
/Zephyr-latest/samples/net/sockets/big_http_download/ |
D | README.rst | 50 infinite loop), while the total counter of the bytes received is kept.
|
/Zephyr-latest/boards/adi/max32672evkit/doc/ |
D | index.rst | 214 … | Disconnects power from VCORE from an external power supply through test loop TP6.| | 216 …| | | Connects power to VCORE from an external power supply through test loop TP6. | …
|
/Zephyr-latest/lib/heap/ |
D | Kconfig | 35 int "Number of tries in the inner heap allocation loop"
|
/Zephyr-latest/doc/kernel/services/timing/ |
D | clocks.rst | 303 timeout and loop, waiting for it to finish while doing some processing 330 an uptime tick at which it will expire. So such a loop might look like: 367 value, and should never be called iteratively in a loop.
|
/Zephyr-latest/cmake/compiler/iar/ |
D | compiler_flags.cmake | 41 --diag_suppress=Pe128 # loop is not reachable
|
/Zephyr-latest/boards/arduino/opta/doc/ |
D | index.rst | 174 void loop() { }
|
/Zephyr-latest/modules/cmsis-dsp/ |
D | Kconfig | 289 This option enables manual loop unrolling in the DSP functions.
|
/Zephyr-latest/boards/gaisler/gr716a_mini/doc/ |
D | index.rst | 110 GR716 Phase-locked loop Cobham Gaisler
|
/Zephyr-latest/doc/hardware/porting/ |
D | arch.rst | 168 can possibly occur. The handler can be as simple as a spinning loop. However, 430 This function can be called in a loop within a context that does not care if it 435 for doing real work after initialization, i.e. it is sitting in a loop doing 871 #. Functions for entering and exiting GDB stub main loop. 875 will serve as the entry point to GDB stub main loop. 881 execution context to go into the GDB stub main loop to receive commands
|
/Zephyr-latest/doc/kernel/services/scheduling/ |
D | index.rst | 288 be called within a loop. Note that in certain architectures, upon return, 352 * go to next loop iteration (the semaphore might have been given
|
/Zephyr-latest/boards/nxp/s32z2xxdc2/support/ |
D | startup.cmm | 123 ; Write loop to self instruction
|
/Zephyr-latest/subsys/testsuite/ztest/ |
D | Kconfig | 106 spin in a loop. This is useful for low power mode tests, where
|
12345