Home
last modified time | relevance | path

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

123

/Zephyr-latest/subsys/shell/
DKconfig.template.shell_log_queue_size10 slow shell transport may lead to situations where logs are dropped
/Zephyr-latest/dts/bindings/counter/
Despressif,esp32-rtc-timer.yaml11 such situations.
/Zephyr-latest/dts/bindings/wifi/
Despressif,esp-at.yaml20 Modem is reset by an external source. In most situations this will
/Zephyr-latest/subsys/emul/
DKconfig22 handle these situations correctly. Test coverage can therefore
/Zephyr-latest/doc/project/
Dcommunication.rst13 and open. Mailing lists are always available for use in situations where
/Zephyr-latest/doc/hardware/peripherals/
Dregulators.rst17 client. For those situations the cost of using the regulator device
/Zephyr-latest/tests/kernel/timer/starve/
DREADME.txt4 correctly handles situations where only one timeout is present, and that
/Zephyr-latest/dts/bindings/iio/afe/
Dvoltage-divider.yaml47 default value of 100us should be sufficient in most situations.
/Zephyr-latest/arch/arm/core/cortex_m/
Dthread_abort.c40 * situations where the isr check is true but there in z_impl_k_thread_abort()
/Zephyr-latest/subsys/random/
Drandom_entropy_device.c37 * still be gathering entropy during early boot situations. in rand_get()
/Zephyr-latest/drivers/console/
Drtt_console.c49 * These two situations are distinguished using the following in rtt_console_out()
/Zephyr-latest/include/zephyr/logging/
Dlog.h49 * @details It's meant to register messages related to unusual situations that
80 * @details It's meant for situations that warrant investigation but could clutter
138 * messages related to unusual situations that are not necessarily errors.
193 * @details It's meant to register messages related to unusual situations that
248 * @details It's meant to register messages related to unusual situations that
/Zephyr-latest/doc/services/resource_management/
Dindex.rst6 There are various situations where it's necessary to coordinate resource
/Zephyr-latest/tests/kernel/mem_slab/mslab_threadsafe/src/
Dtest_mslab_threadsafe.c22 * allocating 3 blocks each, so it's possible in exhaustion situations
/Zephyr-latest/samples/subsys/smf/smf_calculator/
DREADME.rst15 This uses a three-layer hierarchical statechart to handle situations such as
/Zephyr-latest/lib/heap/
DKconfig42 more successful allocations in situations of high
/Zephyr-latest/subsys/usb/device/
DKconfig146 This prevents deadlock situations where tasks on the system
/Zephyr-latest/kernel/
DKconfig.smp21 provide arch_swap. In uniprocess situations where the
/Zephyr-latest/doc/kernel/data_structures/
Drbtree.rst8 For these situations, Zephyr provides a balanced tree implementation
/Zephyr-latest/scripts/west_commands/runners/
Dmdb.py56 # for MDB. This is useful for troubleshooting situations with
/Zephyr-latest/tests/kernel/semaphore/sys_sem/src/
Dmain.c71 * @details Using semaphore with some situations
/Zephyr-latest/doc/build/dts/
Dhowtos.rst124 In some situations the device cannot be known at build-time, e.g., if it depends
152 devicetree. In some situations your code will compile but it will fail to link
172 help in such situations. Note that you can also use :c:func:`device_get_binding`
/Zephyr-latest/doc/develop/
Denv_vars.rst224 may be useful in such situations:
/Zephyr-latest/doc/hardware/cache/
Dguide.rst6 This section discusses the basics of cache coherency and under what situations a
/Zephyr-latest/doc/hardware/emulator/
Dbus_emulators.rst21 handle these situations correctly. Test coverage can therefore

123