Searched refs:cases (Results 201 – 225 of 248) sorted by relevance
12345678910
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig | 1008 the size of net_pkt so in typical cases you should not enable it.
1033 the size of net_pkt so in typical cases you should not enable it.
|
| /Zephyr-latest/doc/develop/west/ |
| D | build-flash-debug.rst | 801 The test cases in :zephyr_file:`scripts/west_commands/tests` add unit test
805 changes break existing test cases, CI testing on upstream pull
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | mcp.rst | 22 Note that in the examples below, in many cases the debug output has
|
| /Zephyr-latest/samples/subsys/mgmt/updatehub/ |
| D | README.rst | 380 cases are server down, missing network routes and forget to change the
|
| /Zephyr-latest/doc/services/pm/ |
| D | device.rst | 58 operations that require a device to remain powered on. In such cases,
|
| /Zephyr-latest/boards/phytec/reel_board/doc/ |
| D | index.rst | 18 Zephyr OS in these kinds of use cases:
|
| /Zephyr-latest/subsys/shell/backends/ |
| D | Kconfig.backends | 116 time incoming data. 4 should be enough for almost all the cases unless
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-3.3.rst | 419 edge cases.
704 * DMA API start/stop are defined to be repeatable callable with test cases added.
734 waits for the flash to become ready before continuing. In cases where a
982 device tree node to achieve a 48MHz bus clock. Note that, in most cases, core clock
1113 * Removed :kconfig:option:`CONFIG_NET_CONFIG_SETTINGS` use from test cases to
2365 be present in responses and in cases where there is only an ``rc`` result,
2908 * :github:`54454` - Twister summary in some cases provides an irrelevant example
3501 * :github:`50567` - Passed test cases are reported as "Skipped" because of incomplete test log
3504 * :github:`50525` - Passed test cases reported as "Skipped" because test log lost
3505 * :github:`50515` - Non-existing test cases reported as "Skipped" with reason “No results captured…
|
| D | release-notes-2.5.rst | 498 * Fixed cases where socket would not close.
1735 …ub:`27583` - sanitycheck does not fail on SRAM overflow, add option to make it fail on those cases.
1818 * :github:`25832` - [test][kernel][lpcxpresso55s69_ns] kernel cases meet ESF could not be retrieved…
1869 * :github:`21216` - Ztest "1cpu" cases don't retarget interrupts on x86_64
1954 * :github:`6648` - Trusted Execution Framework: practical use-cases (high-level overview)
|
| D | release-notes-1.12.rst | 264 * Added description for kernel test cases through extensive doxygen comments
554 * :github:`7026` - i2c based sensor test cases fails on arc core
|
| D | release-notes-1.14.rst | 576 cases have been appropriately converted to use memory domains.
1601 * :github:`13166` - tests/kernel/threads/dynamic_thread test cases are failing on frdm_k64f board
2040 * :github:`10537` - nRF52 regression: random resets noted across several boards / use cases
2051 * :github:`10475` - tests/kernel/threads/dynamic_thread test cases are failing on ARM boards
2052 * :github:`10474` - tests/kernel/pipe/pipe test cases are failing on ARM boards
|
| D | release-notes-1.10.rst | 488 * :github:`4853` - cmake: building unit test cases ignore EXTRA_* settings
|
| D | release-notes-2.6.rst | 1333 * :github:`34662` - many udp networking cases fail on nxp platforms
1485 …wr_ke18f: tests/kernel/sched/schedule_api - kernel_threads_sched_userspace cases meet out our space
1565 …010_evk: tests/kernel/sched/schedule_api - kernel_threads_sched_userspace cases meet out our space
1677 * :github:`33176` - tests: kernel: Multiple test cases from tests/kernel/workq/work_queue are faili…
|
| /Zephyr-latest/doc/build/dts/ |
| D | macros.bnf | 318 ; The different cases are not exhaustively documented here to avoid
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/audio/ |
| D | bluetooth-le-audio-arch.rst | 1164 In cases like this the application is only notified about the change with a callback,
1221 Response, and where support for Write Long Characteristic Value is optional in most cases.
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | mailboxes.rst | 350 left unchanged. In all cases the mailbox updates the receiving thread's
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 413 The following sections discuss various common edge-cases and nuances and how to handle them.
|
| /Zephyr-latest/boards/espressif/esp_wrover_kit/doc/ |
| D | index.rst | 198 In other cases, peripherals can coexist under certain conditions. This is applicable to, for
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 985 cases where the file is an original to Zephyr, the commit message should
991 In cases where the file is :ref:`imported from an external project
|
| /Zephyr-latest/doc/project/ |
| D | release_process.rst | 109 that have been overlooked, or that are new, and in these cases, the criteria
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 1045 In cases where board support is incomplete, flashing via the Zephyr build
1118 In cases where the board or platform you are developing for is not yet
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | index.rst | 88 In some cases a thread may want to sleep until another thread terminates.
|
| /Zephyr-latest/doc/connectivity/usb/device/ |
| D | usb_device.rst | 76 Below is a description of the different use cases and some pitfalls.
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 63 sysbuild can direct them to the right build system. In some cases, such as
|
| /Zephyr-latest/subsys/bluetooth/controller/ |
| D | Kconfig | 156 cases, like for unit testing.
|
12345678910
