Searched full:rare (Results 1 – 22 of 22) sorted by relevance
| /Zephyr-latest/dts/bindings/mipi-dbi/ |
| D | zephyr,mipi-dbi-spi.yaml | 34 On rare types of SPI interfaces, discrete shift registers can be found
|
| /Zephyr-latest/include/zephyr/bluetooth/audio/ |
| D | ccid.h | 45 * may (in very rare cases) result in duplicated CCIDs on the device.
|
| /Zephyr-latest/drivers/wifi/nrf_wifi/ |
| D | CMakeLists.txt | 71 # but as its rare and not seen in most cases, we can disable it.
|
| /Zephyr-latest/drivers/fuel_gauge/sbs_gauge/ |
| D | sbs_gauge.h | 59 * is rare, and most will have a payload size of 2.
|
| /Zephyr-latest/scripts/tests/twister_blackbox/ |
| D | test_tooling.py | 61 # nsim_vpx5 is one of the rare platforms that do not support the zephyr toolchain
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | rbtree.rst | 115 a memory allocation API, are quite rare in the industry and are
|
| /Zephyr-latest/scripts/native_simulator/common/src/ |
| D | nct.c | 691 * the load of the host. Without them, very rare & mysterious segfault crashes
706 * In some very rare cases in very loaded machines, a race in the glibc pthread_cancel()
713 * Therefore we do not do this, to avoid this very rare crashes.
|
| /Zephyr-latest/arch/arc/core/ |
| D | arc_connect.c | 72 * In rare case, multiple concurrent ICIs sent to same target can in z_arc_connect_ici_clear()
|
| /Zephyr-latest/kernel/ |
| D | atomic_c.c | 34 /* For those rare CPUs which support user mode, but not native atomic
|
| D | thread.c | 378 /* This is so rare not bothering for now */
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-le-host.rst | 280 simplifies error handling by reducing rare failure conditions to a common
|
| /Zephyr-latest/include/zephyr/dt-bindings/mipi_dbi/ |
| D | mipi_dbi.h | 154 * SPI transfer of DBI commands as 16-bit blocks, a rare and seldom behaviour
|
| /Zephyr-latest/drivers/usb/device/ |
| D | usb_dc_rpi_pico.c | 195 * transaction is sent, however in some rare cases from the perspective in udc_rpi_handle_setup()
208 /* This warning could be triggered by the rare event described in udc_rpi_handle_setup()
|
| /Zephyr-latest/drivers/timer/ |
| D | cortex_m_systick.c | 185 /* Rare case, when the interrupt was triggered, with previously programmed in sys_clock_isr()
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | tips.rst | 307 Rare exceptions might include cases where you're sure that the dependencies
446 set to a custom value in rare circumstances, then add another option for
|
| /Zephyr-latest/doc/project/ |
| D | release_process.rst | 80 occasions are rare and require a TSC approval and a justification. As a general
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | workqueue.rst | 525 A rare case where you could safely use :c:func:`k_work_is_pending` is as a
|
| /Zephyr-latest/scripts/kconfig/ |
| D | guiconfig.py | 1162 # rare cases, but is fast and flicker-free.
|
| D | kconfiglib.py | 2508 # Very rare
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-3.5.rst | 267 * Fixed ULL stuck in semaphore under rare conditions
|
| D | release-notes-2.0.rst | 942 * :github:`16915` - stack_sentinel: rare ASSERTION FAIL [!(z_arch_curr_cpu()->nested != 0U)] @ ZEPH…
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | att.c | 3161 * for developers. This reduces rare failure conditions to a common one, allowing developers in att_timeout()
|
