Searched refs:cases (Results 51 – 75 of 248) sorted by relevance
12345678910
| /Zephyr-latest/soc/nxp/lpc/lpc55xxx/ |
| D | Kconfig | 99 this PLL should not be used as the core clock in those cases.
|
| /Zephyr-latest/samples/basic/custom_dts_binding/ |
| D | README.rst | 18 For typical use cases like LEDs or buttons, the existing :dtcompatible:`gpio-leds` or
|
| /Zephyr-latest/samples/basic/blinky_pwm/ |
| D | README.rst | 37 In these other cases, however, manual wiring is necessary:
|
| /Zephyr-latest/doc/develop/api/ |
| D | design_guidelines.rst | 36 cases further context can accessed by the callback indirectly by
90 In the cases where the function is used but not enabled the definition
|
| /Zephyr-latest/doc/services/ |
| D | secure_storage.rst | 37 * does not guarantee that the data it stores will be secure at rest in all cases.
60 However, this does not guarantee that the data stored will be secure at rest in all cases,
|
| /Zephyr-latest/boards/lowrisc/opentitan_earlgrey/doc/ |
| D | index.rst | 10 designed for several use cases requiring hardware security. The `OpenTitan
|
| /Zephyr-latest/samples/boards/nordic/battery/ |
| D | README.rst | 45 Note that in many cases where there is no voltage divider the digital
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.native_posix | 23 to create multiple interfaces in certain use cases. For example if
|
| /Zephyr-latest/boards/amd/acp_6_0_adsp/doc/ |
| D | index.rst | 7 Zephyr OS is ported to run various audio and speech use cases on
|
| /Zephyr-latest/doc/contribute/ |
| D | proposals_and_rfcs.rst | 49 the `Zephyr meetings`_ in order to move it forward in cases where there is
|
| /Zephyr-latest/doc/build/dts/ |
| D | zephyr-user-node.rst | 55 be able to reconfigure which devices your application uses in simple cases
|
| /Zephyr-latest/drivers/ieee802154/ |
| D | Kconfig | 36 be built). Used only for very specific cases, such as wpan_serial
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.x86 | 46 counter with comparator eliminates almost all edge cases
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | fetch_and_get.rst | 69 In all cases it's very likely there will be variable delays from the actual
|
| /Zephyr-latest/doc/services/rtio/ |
| D | index.rst | 136 In some cases requests to read may not know how much data will be produced.
138 the frequency of the data is unpredictable. In these cases it may be wasteful
205 RTIO is useful in cases where concurrent or batch like I/O flows are useful.
|
| /Zephyr-latest/subsys/logging/frontends/ |
| D | Kconfig | 82 Option can be enabled for memory constraint cases to remove all logging
|
| /Zephyr-latest/cmake/modules/ |
| D | FindHostTools.cmake | 65 # in the mcuboot repository if that's present in some cases)
|
| D | unittest.cmake | 33 # In both cases, it is safe to do a separate_arguments on the argument.
|
| D | zephyr_default.cmake | 129 # This is done twice to support cases where the content of `${module}` itself
|
| /Zephyr-latest/boards/native/native_posix/doc/ |
| D | index.rst | 29 :ref:`native_sim<native_sim>` supports all ``native_posix`` use cases.
|
| /Zephyr-latest/doc/services/llext/ |
| D | build.rst | 15 In some cases, involving the full Zephyr build system may not be feasible or
163 different use cases, such as when building mocks for unit tests:
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.vm | 53 build-time cases, or when a physical address cannot be looked up
74 for mapping driver MMIO regions, as well as special RAM mapping use-cases
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | coap_client.rst | 50 The callback provided in the callback will be called in following cases:
|
| /Zephyr-latest/samples/boards/nxp/s32/netc/ |
| D | README.rst | 10 for the different use-cases:
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | networking_with_host.rst | 35 in some cases, you might need to use the SLIP method for host connectivity.
|
12345678910
