Home
last modified time | relevance | path

Searched refs:heavy (Results 1 – 13 of 13) sorted by relevance

/Zephyr-latest/samples/boards/st/i2c_timing/
DREADME.rst23 Because the code sequence to calculate the I2C V2 TIMING value is heavy,
/Zephyr-latest/subsys/logging/backends/
DKconfig.rtt79 case of heavy traffic data can be lost and it may be necessary to
/Zephyr-latest/samples/modules/lvgl/demos/
DREADME.rst17 …usage, and so on. It can be used if there is any memory corruption during heavy usage or any memor…
/Zephyr-latest/drivers/console/
DKconfig155 heavy traffic data can be lost and it may be necessary to increase
162 assumes that RTT session is active. In case of heavy traffic data can
/Zephyr-latest/drivers/modem/
DKconfig62 Enabling this setting will turn on VERY heavy debugging from the
/Zephyr-latest/modules/hostap/
DKconfig54 # Supplicant API is stack heavy (buffers + snprintfs) and control interface
/Zephyr-latest/subsys/bluetooth/common/
DKconfig163 a pool is that the if there is a heavy inflow of such events
/Zephyr-latest/subsys/shell/backends/
DKconfig.backends228 case of heavy traffic data can be lost and it may be necessary to
/Zephyr-latest/drivers/wifi/nrf_wifi/
DKconfig.nrfwifi749 depending on the delay. It is ideal for heavy buffered traffic.
/Zephyr-latest/doc/releases/
Drelease-notes-3.7.rst886 block depending on the clock configuration in use. To avoid embedding this heavy algorithm
1549 * Improved debug logs, so that they're easier to follow under heavy load.
Drelease-notes-2.0.rst581 * :github:`18524` - No disconnection event during "heavy" indication stream
Drelease-notes-2.4.rst184 * This infrastructure is still under heavy development.
Drelease-notes-3.1.rst1393 * :github:`45463` - null function pointer called when using shell logger backend under heavy load