| /Zephyr-latest/boards/luatos/esp32c3_luatos_core/doc/ |
| D | index.rst | 14 but it also facilitates a variety of use-cases based on dual connectivity. [1]_
|
| /Zephyr-latest/boards/st/stm32g081b_eval/doc/ |
| D | index.rst | 30 through various use cases.
|
| /Zephyr-latest/arch/arm/ |
| D | Kconfig | 75 A default value of 0x00000000 might work in most cases as SOCs have an alias
|
| /Zephyr-latest/boards/espressif/esp32c3_devkitc/doc/ |
| D | index.rst | 18 but it also facilitates a variety of use-cases based on dual connectivity.
|
| /Zephyr-latest/boards/espressif/esp32c3_devkitm/doc/ |
| D | index.rst | 18 but it also facilitates a variety of use-cases based on dual connectivity.
|
| /Zephyr-latest/doc/contribute/ |
| D | contributor_expectations.rst | 112 be added to the automated test suite. All API functions should have test cases
208 In cases where a contributor objects to change requests from reviewers, Zephyr
|
| /Zephyr-latest/doc/services/logging/ |
| D | cs_stm.rst | 65 There may be cases when logging is too slow (even though it is very fast). For cases like that a de…
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | runner.py | 151 selected_cases = self.cases - self.filtered_cases
213 def cases(self): member in ExecutionCounter
217 @cases.setter
218 def cases(self, value): member in ExecutionCounter
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.7.rst | 418 * ``ZEP-1707`` - [PTS] 7 SM/MAS cases fail
434 * ``ZEP-1764`` - samples: sample cases use hard code device name, such as "GPIOB" "I2C_0"
435 * ``ZEP-1768`` - samples: cases miss testcase.ini
|
| D | release-notes-1.9.rst | 223 * ``ZEP-1843`` - provide mechanism to filter test cases based on available hardware
320 * ``ZEP-2398`` - network stack test cases are only tested on x86
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | rbtree.rst | 99 elaborate code to handle the edge cases (for example, one swapped node
|
| /Zephyr-latest/doc/develop/tools/ |
| D | coccinelle.rst | 319 * A more detailed information about the script with exceptional cases
327 //# This makes an effort to find cases where ARRAY_SIZE can be used such as
|
| /Zephyr-latest/doc/build/dts/api/ |
| D | api.rst | 373 is usually for backwards compatibility in cases when the Kconfig option
374 predates devicetree support in Zephyr. In other cases, there is no Kconfig
|
| /Zephyr-latest/doc/build/dts/ |
| D | intro-syntax-structure.rst | 14 understand some detailed cases.
67 Property values can be any sequence of bytes. In some cases, the values are an
|
| /Zephyr-latest/doc/build/ |
| D | zephyr_cmake_package.rst | 250 and Zephyr workspace applications. Specifying a version in those cases ensures the
330 cases, such as loading of additional CMake boilerplate code.
|
| /Zephyr-latest/doc/develop/api/ |
| D | terminology.rst | 163 required behavior. In many cases it would also check
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | arm-scmi.rst | 28 agents and provide the necessary functionality. In some cases, the requests
|
| /Zephyr-latest/doc/hardware/cache/ |
| D | guide.rst | 157 In some cases, the same buffer may be reused for e.g. DMA reads and DMA writes.
|
| /Zephyr-latest/doc/services/crypto/ |
| D | psa_crypto.rst | 86 caller. There are several use cases; ranging from attestation of the
|
| /Zephyr-latest/doc/services/input/ |
| D | gpio-kbd.rst | 134 In more extreme cases, such as if the columns are using a multiplexer and it's
|
| /Zephyr-latest/subsys/testsuite/ztest/ |
| D | Kconfig | 43 value. Please be aware that increasing it for long-running test cases
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | clocks.rst | 249 a timeout), but may be a performance problem in some cases. The
358 past. For simple cases, :c:func:`sys_timepoint_expired` can be used as well.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | tls_credentials_shell.rst | 249 The remaining three formats are provided for convenience in special use-cases.
|
| /Zephyr-latest/doc/services/pm/ |
| D | device_runtime.rst | 95 suspend the device if necessary. It is worth to note that in both cases, the
|
| /Zephyr-latest/doc/services/debugging/ |
| D | gdbstub.rst | 91 test cases ``debug.gdbstub.breakpoints`` demonstrating how the Zephyr GDB stub can be used.
|
