Searched refs:cases (Results 176 – 200 of 248) sorted by relevance
12345678910
| /Zephyr-latest/doc/develop/west/ |
| D | workspaces.rst | 58 The following sections cover common cases for running ``west update`` without
|
| /Zephyr-latest/boards/udoo/udoo_neo_full/doc/ |
| D | index.rst | 228 work with Zephyr applications in most cases. The reason is that there is
|
| /Zephyr-latest/cmake/modules/ |
| D | dts.cmake | 32 # See the specific API documentation for each of these cases for more
|
| /Zephyr-latest/doc/connectivity/usb/device_next/ |
| D | usb_device.rst | 134 :c:enumerator:`USBD_SPEED_HS` and the configuration number. For simple cases,
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-3.2.rst | 713 * Fixed the nRF PWM driver to properly handle cases where PWM generation is
1778 - :github:`50515` - Non-existing test cases reported as "Skipped" with reason “No results captured…
1782 - :github:`50567` - Passed test cases are reported as "Skipped" because of incomplete test log
1836 * :github:`50525` - Passed test cases reported as "Skipped" because test log lost
1879 * :github:`50218` - rcar_h3ulcb: can: failed to run RTR test cases
2030 * :github:`49136` - L2CAP ecred test cases failed.
2089 * :github:`48801` - test: driver: wdt: wdt cases fails in LPC platform randonly
2258 * :github:`47292` - it8xxx2_evb: many test cases failed probably due to the west update
2421 * :github:`46157` - ACRN: some cases still failed because of the log missing
2518 …github:`43928` - pm: going to PM_STATE_SOFT_OFF in pm_policy_next_state causes assert in some cases
|
| D | release-notes-1.5.rst | 141 * ``ZEP-271`` - nios2: enable microkernel & test cases
|
| D | release-notes-1.8.rst | 246 * ``ZEP-1721`` - many TinyCrypt test cases only run on ARM and x86
|
| D | release-notes-2.1.rst | 452 of test cases in existing tests to increase code coverage.
738 * :github:`19284` - Service Changed indication not being sent in some cases
944 * :github:`2490` - Provide sanity test cases for NANO\_ESF/NANO\_ISF structures
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | board_porting.rst | 25 - Support for advanced use cases with :ref:`sysbuild`
59 and works reliably in many cases (though multi-core SoCs may not be handled
960 In some cases you might want to also adjust additional settings, like the
|
| D | arch.rst | 205 Therefore, the context switching must thus be able to handle all these cases.
213 control to another thread. There are two cases where this happens
509 thread running in user mode, as well as any use-cases for kernel stacks.
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | reports.py | 698 results.cases
|
| /Zephyr-latest/subsys/bluetooth/common/ |
| D | Kconfig | 165 block and may even eliminate deadlocks in some cases.
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | kernelobjects.rst | 145 (in many cases, by itself) when it was a supervisor thread.
|
| D | syscalls.rst | 477 In some cases the amount of data isn't known at compile time or may be too
588 in most cases using ``CHECKIF()``.
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-le-host.rst | 282 special cases for ATT timeouts.
|
| /Zephyr-latest/doc/build/dts/ |
| D | phandles.rst | 143 cases** that are handled in devicetree with phandle-array properties.
|
| D | troubleshooting.rst | 173 :zephyr_file:`drivers/i2c/i2c_nrfx_twim.c`. Notice how even in cases where
|
| D | api-usage.rst | 186 similarly, except ``DT_PROP()`` expands to an array initializer in these cases.
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister.rst | 1026 option. In this cases, log messages are captured for example using a script.
1308 cases the detected ID is not the correct one to use, for example when
1427 - Ignore some logic in twister to expand platform coverage in cases where
1536 dependencies between test cases. For native_sim platforms, you can provide
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 19 fact, Zephyr’s build system supports arbitrary use cases related to blobs. This
|
| /Zephyr-latest/modules/trusted-firmware-m/ |
| D | CMakeLists.txt | 291 # file lock mechanism. To ensure correct behaviour in all cases, limit
|
| /Zephyr-latest/doc/build/cmake/ |
| D | index.rst | 20 situations and reconfigure automatically, but there are cases when this must be
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | access.rst | 261 publication delays in the following cases:
|
| /Zephyr-latest/arch/x86/ |
| D | Kconfig | 336 Zephyr test cases assume 3 additional domains can be instantiated.
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | intel_adsp_generic.rst | 33 board in these cases.
|
12345678910
