Searched refs:cases (Results 76 – 100 of 248) sorted by relevance
12345678910
| /Zephyr-latest/samples/modules/lvgl/demos/ |
| D | README.rst | 15 …The benchmark demo tests the performance in various cases. For example rectangle, border, shadow, …
|
| /Zephyr-latest/scripts/tests/twister/ |
| D | test_runner.py | 192 ec.cases = 25
232 assert ec.cases == 25
2105 cases = 0,
2626 cases = 0,
2646 tr.results.cases += value * (-1 if decrement else 1)
2657 assert tr.results.cases == 4
2677 cases = 0,
|
| /Zephyr-latest/doc/kernel/drivers/ |
| D | index.rst | 185 most cases requires that the optional feature be controlled by a
400 In some cases you may just need to run a function at boot. For such cases, the
636 For these cases, DEVICE_MMIO_ROM directives may be omitted.
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | workqueue.rst | 344 For delayed work there are two common use cases, depending on whether a
392 :c:func:`k_work_delayable_busy_get()` some use cases require synchronizing
413 data races: cases where the work thread might inspect or manipulate shared
418 For simple flags :ref:`atomic_v2` may be sufficient. In other cases spin
471 cases it is important to verify that the intended result was obtained.
486 operation did not complete as expected is not a problem. In those cases the
|
| /Zephyr-latest/subsys/logging/ |
| D | Kconfig.misc | 23 Using VLA slightly decreases stack usage in some cases it may not be
|
| /Zephyr-latest/share/zephyr-package/cmake/ |
| D | zephyr_package_search.cmake | 13 # For Zephyr 3.0 and earlier, the Zephyr_DIR might in some cases be
|
| /Zephyr-latest/subsys/bluetooth/ |
| D | Kconfig.iso | 100 In most cases the default value of 2 is a safe bet.
|
| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | semaphores.rst | 45 is incremented. All standard use cases of the common semaphore are supported.
|
| /Zephyr-latest/cmake/linker/armlink/ |
| D | target.cmake | 105 # address which in some cases leads to overlapping section errors.
|
| /Zephyr-latest/cmake/modules/ |
| D | shields.cmake | 118 # This command prints all shields in the system in the following cases:
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | extensions.rst | 83 For cases where it's okay for a pattern to match no files (or for a plain
|
| /Zephyr-latest/cmake/bintools/ |
| D | bintools_template.cmake | 37 # However, there might be tools and/or use cases where the current property
38 # scheme does not cover the exact needs. For those use-cases it is possible
|
| /Zephyr-latest/drivers/wifi/esp32/ |
| D | Kconfig.esp32 | 97 application can process them. In these cases we may run out of memory if
146 In these cases, we may run out of TX buffers.
175 than WiFi layer can transmit. In these cases, we may run out of TX
|
| /Zephyr-latest/doc/hardware/pinctrl/ |
| D | index.rst | 100 device driver requirements. In many cases a single state applied at
101 initialization time will be sufficient, but in some other cases more will be
103 established for the most common use cases. The figure below
145 the compiled firmware. However, there are some cases where certain states will
|
| /Zephyr-latest/lib/heap/ |
| D | Kconfig | 87 - "auto" providing optimal memory overhead in all cases but with
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | overview.rst | 15 Example use-cases of Zephyr's user mode features:
175 at build time if they are to be used from user mode. Dynamic use-cases for
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | soc_porting.rst | 35 and check that it's not already in use. In some cases someone else may have
227 other SoC related Kconfig settings. In some cases a SOC_PART_NUMBER.
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-3.0.rst | 958 * :github:`42010` - intel_adsp_cavs18: Test cases failed on SMP related test cases (when CONFIG_MP_…
960 * :github:`41993` - Intel_adsp_cavs18: test cases can not get complete log
962 * :github:`41991` - Intel_adsp_cavs18: some test cases can not get any log
971 * :github:`41943` - Intel_adsp_cavs15: all the test cases run failed when running them by twister
986 * :github:`41835` - UP squared and acrn_ehl_crb: test cases which have config SMP config failed
1043 * :github:`41317` - ADSP: Many kernel test cases which have CONFIG_MP_NUM_CPUS=1 failed in daily te…
1085 * :github:`40917` - twister --export-tests export all cases even this case can not run on given pla…
1111 * :github:`40724` - tests: logging: logging test cases failed in multiple boards
1120 …0643` - intel_adsp_cavs15: the zephyr_pre0.elf is quite large (530MB) on ADSP for some test cases
1165 * :github:`40169` - drivers: can: net: compilation broken and no test cases in CI
|
| /Zephyr-latest/doc/develop/west/ |
| D | why.rst | 115 - **Clearly specified**: West's behavior in cases where it wraps other
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | rtc.rst | 44 broken-down time, unnecessarily in some cases, and some common
|
| /Zephyr-latest/samples/philosophers/ |
| D | README.rst | 39 In these cases, the philosopher threads will run with priorities 0 to 5 (preempt-only) and -7 to -2
|
| /Zephyr-latest/doc/services/ipc/ipc_service/ |
| D | ipc_service.rst | 166 subsets of features for specific use cases.
|
| /Zephyr-latest/subsys/net/l2/ethernet/ |
| D | Kconfig | 78 in some cases. A gratuitous ARP request is a ARP request packet where
|
| /Zephyr-latest/boards/nordic/thingy53/ |
| D | thingy53_nrf5340_common.dtsi | 259 /* UART0 GPIOs can be configured for other use-cases */
|
| /Zephyr-latest/tests/subsys/logging/log_blocking/ |
| D | REAME.md | 15 > and should only be attempted in advanced use cases.
|
12345678910
