Searched refs:underlying (Results 1 – 25 of 69) sorted by relevance
123
| /Zephyr-latest/tests/subsys/sensing/boards/ |
| D | native_sim.overlay | 35 underlying-device = <&bmi160_i2c>;
44 underlying-device = <&bmi160_spi>;
|
| /Zephyr-latest/samples/subsys/sensing/simple/boards/ |
| D | native_sim.overlay | 35 underlying-device = <&bmi160_i2c>;
44 underlying-device = <&bmi160_spi>;
|
| /Zephyr-latest/samples/net/openthread/ |
| D | README.rst | 5 These samples demonstrate various use cases for the Thread protocol and underlying IEEE 802.15.4.
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 75 /* Cause your underlying technology to associate */
78 /* Cause your underlying technology to disassociate */
81 /* Perform any required initialization for your underlying technology */
193 …disable or enable these features, regardless of the inherent behavior of the underlying technology.
194 In other words, no matter how the underlying technology behaves, your implementation must make it a…
253 …* The connectivity implementation does not need to update iface dormancy if the underlying :ref:`L…
276 In other words, it should be possible for an application to directly use your underlying technology…
284 …For instance, if an application directly instructs an underlying technology to disassociate, it wo…
308 If the underlying technology cannot be made ready for connect commands immediately when :c:member:`…
410 …t fully conform to that description, regardless of the behavior of the underlying connectivity tec…
[all …]
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.mem | 33 Note: This feature depends on hardware MMU support. If the underlying platform does not
48 underlying platform does not support an MMU or DEMAND_PAGING, then affected POSIX API
61 Note: This feature depends on hardware MMU support. If the underlying platform does not
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | queues.rst | 8 to a FIFO and serves as the underlying implementation for both :ref:`k_fifo
|
| /Zephyr-latest/samples/net/openthread/shell/ |
| D | README.rst | 10 This sample allows testing the Thread protocol and the underlying IEEE 802.15.4 drivers for various
|
| /Zephyr-latest/subsys/fs/ |
| D | Kconfig | 10 Link in the underlying file system libraries. This can be
12 to work directly with the underlying file system libraries.
51 the underlying storage device is initialized.
|
| /Zephyr-latest/samples/subsys/sensing/simple/ |
| D | README.rst | 11 two sensors, with the underlying device bmi160 emulator, and gets the sensor
|
| /Zephyr-latest/subsys/net/l2/wifi/ |
| D | Kconfig | 46 This is typically used when the underlying hardware is not certified for
48 it depends on the underlying chip implementation to support and honour
57 This can be set based on the underlying chipsets limitations.
|
| /Zephyr-latest/arch/posix/ |
| D | Kconfig | 22 thread stack, the real stack is the native underlying pthread stack.
|
| /Zephyr-latest/tests/subsys/sd/sdmmc/ |
| D | README.txt | 6 subsystem. Due to the differences between underlying SD host controller drivers,
|
| /Zephyr-latest/tests/subsys/sd/mmc/ |
| D | README.txt | 6 subsystem. Due to the differences between underlying SD host controller drivers,
|
| /Zephyr-latest/samples/subsys/demand_paging/ |
| D | README.rst | 49 To actually view the underlying demand paging subsystem at work, debug
|
| /Zephyr-latest/soc/mediatek/mt8xxx/ |
| D | CMakeLists.txt | 16 # Sign zephyr.ri using west (if the underlying rimage tool is
|
| /Zephyr-latest/doc/services/modem/ |
| D | index.rst | 25 to abstract away its underlying mechanism.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | thread.rst | 45 testing and debugging Thread and its underlying IEEE 802.15.4 drivers.
|
| D | sockets.rst | 264 should be created. The underlying socket can then be bound to a particular
275 * The underlying socket is a "dispatcher" socket now.
283 /* The underlying socket is "dispatched" to a particular network interface
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.mem_domain | 53 tables, these APIs don't need to be implemented as the underlying
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | smp_protocol.rst | 9 SMP is an application layer protocol. The underlying transport layer is not
21 header may be used for reassembly purposes if underlying transport layer supports
|
| /Zephyr-latest/doc/connectivity/usb/host/ |
| D | usbip.rst | 13 USB/IP uses TCP/IP. Both of the underlying connectivity stacks, USB and
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | blob.rst | 8 from a single source to many Target nodes over the Bluetooth Mesh network. It is the underlying
17 BLOB transfers are constrained by the transfer speed and reliability of the underlying mesh network.
53 authentication of the BLOB data. However, the underlying encryption of the Bluetooth Mesh protocol
|
| /Zephyr-latest/doc/services/storage/fcb/ |
| D | fcb.rst | 30 until existing data has been collected. FCB treats underlying storage as
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | heap.rst | 49 The underlying implementation of the :c:struct:`k_heap`
117 and repurpose the underlying memory for another usage.
126 application-provided callback is responsible for doing the underlying
|
| /Zephyr-latest/doc/services/crypto/ |
| D | psa_crypto.rst | 20 open-source cryptographic library that provides the underlying
46 The PSA Crypto API abstracts the underlying cryptographic library,
|
123
