Home
last modified time | relevance | path

Searched full:situations (Results 1 – 25 of 52) sorted by relevance

123

/Zephyr-Core-3.5.0/subsys/shell/
DKconfig.template.shell_log_queue_size10 slow shell transport may lead to situations where logs are dropped
/Zephyr-Core-3.5.0/subsys/random/
Drand32_entropy_device.c30 * still be gathering entropy during early boot situations. in z_impl_sys_rand32_get()
62 * still be gathering entropy during early boot situations. in rand_get()
/Zephyr-Core-3.5.0/dts/bindings/wifi/
Despressif,esp-at.yaml20 Modem is reset by an external source. In most situations this will
/Zephyr-Core-3.5.0/dts/bindings/counter/
Despressif,esp32-rtc-timer.yaml11 such situations.
/Zephyr-Core-3.5.0/doc/project/
Dcommunication.rst13 and open. Mailing lists are always available for use in situations where
/Zephyr-Core-3.5.0/subsys/emul/
DKconfig22 handle these situations correctly. Test coverage can therefore
/Zephyr-Core-3.5.0/doc/hardware/peripherals/
Dregulators.rst17 client. For those situations the cost of using the regulator device
/Zephyr-Core-3.5.0/tests/kernel/timer/starve/
DREADME.txt4 correctly handles situations where only one timeout is present, and that
/Zephyr-Core-3.5.0/arch/arm/core/cortex_m/
Dthread_abort.c38 * situations where the isr check is true but there in z_impl_k_thread_abort()
/Zephyr-Core-3.5.0/drivers/console/
Drtt_console.c52 * These two situations are distinguished using the following in rtt_console_out()
/Zephyr-Core-3.5.0/include/zephyr/logging/
Dlog.h47 * @details It's meant to register messages related to unusual situations that
118 * messages related to unusual situations that are not necessarily errors.
173 * @details It's meant to register messages related to unusual situations that
228 * @details It's meant to register messages related to unusual situations that
/Zephyr-Core-3.5.0/doc/services/resource_management/
Dindex.rst6 There are various situations where it's necessary to coordinate resource
/Zephyr-Core-3.5.0/tests/kernel/mem_slab/mslab_threadsafe/src/
Dtest_mslab_threadsafe.c22 * allocating 3 blocks each, so it's possible in exhaustion situations
/Zephyr-Core-3.5.0/subsys/usb/device/
DKconfig129 This prevents deadlock situations where tasks on the system
/Zephyr-Core-3.5.0/lib/os/
DKconfig.heap24 more successful allocations in situations of high
/Zephyr-Core-3.5.0/scripts/west_commands/runners/
Dmdb.py45 # for MDB. This is useful for troubleshooting situations with
/Zephyr-Core-3.5.0/doc/kernel/data_structures/
Drbtree.rst8 For these situations, Zephyr provides a balanced tree implementation
/Zephyr-Core-3.5.0/doc/hardware/emulator/
Dindex.rst21 handle these situations correctly. Test coverage can therefore
/Zephyr-Core-3.5.0/tests/kernel/semaphore/sys_sem/src/
Dmain.c71 * @details Using semaphore with some situations
/Zephyr-Core-3.5.0/include/zephyr/dt-bindings/pinctrl/
Dnrf-pinctrl.h210 * This can be useful in situations where code running before Zephyr, e.g. a bootloader
/Zephyr-Core-3.5.0/doc/build/dts/
Dhowtos.rst123 In some situations the device cannot be known at build-time, e.g., if it depends
151 devicetree. In some situations your code will compile but it will fail to link
171 help in such situations. Note that you can also use :c:func:`device_get_binding`
/Zephyr-Core-3.5.0/doc/develop/
Denv_vars.rst224 may be useful in such situations:
/Zephyr-Core-3.5.0/doc/connectivity/networking/api/
Dnet_l2.rst154 - L1 -> L2: There are several situations in which the driver needs to initiate
/Zephyr-Core-3.5.0/doc/kernel/memory_management/
Dheap.rst109 For those situations, Zephyr provides a ``sys_multi_heap`` utility.
/Zephyr-Core-3.5.0/kernel/
DKconfig229 Only use this type of allocation in situations
241 situations where malloc is not permitted.
1124 provide arch_swap. In uniprocess situations where the

123