Searched refs:exchange (Results 1 – 25 of 40) sorted by relevance
12
| /Zephyr-latest/subsys/mgmt/mcumgr/transport/ |
| D | Kconfig.bluetooth | 48 bool "Request specific connection parameters for SMP packet exchange"
54 exchange process.
60 int "Minimum connection interval for SMP packet exchange"
64 Minimum connection interval in 1.25ms units used during the exchange of SMP packets.
67 int "Maximum connection interval for SMP packet exchange"
71 Maximum connection interval in 1.25ms units used during the exchange of SMP packets.
74 int "Peripheral latency for SMP packet exchange"
78 Peripheral latency in Connection Intervals used during the exchange of SMP packets.
81 int "Supervision timeout for SMP packet exchange"
85 Supervision timeout in 10ms used during the exchange of SMP packets.
|
| /Zephyr-latest/doc/services/ipc/ipc_service/ |
| D | ipc_service.rst | 10 The IPC service API provides an interface to exchange data between two domains
28 possibly with different priorities, and to use each to exchange data.
47 * Simple data exchange.
48 * Data exchange using the no-copy API.
50 Simple data exchange
102 Data exchange using the no-copy API
|
| /Zephyr-latest/samples/bluetooth/channel_sounding/ |
| D | README.rst | 66 MTU exchange success (247)
70 CS capability exchange completed.
84 MTU exchange success (247)
85 CS capability exchange completed.
103 MTU exchange success (247)
119 MTU exchange success (247)
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | provisioning.rst | 29 * Public key exchange
83 Public key exchange
87 device exchange public keys, either in-band or Out of Band (OOB).
89 In-band public key exchange is a part of the provisioning process and always
92 If the application wants to support public key exchange via OOB, it needs to
98 the public key for the Out of Band exchange, the provisioner may choose to
99 exchange the public key in-band if it can't retrieve the public key via OOB
117 After the initial exchange, the provisioner selects an Out of Band (OOB)
175 Depending on the choice of public key exchange mechanism and authentication method,
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/host/ |
| D | gatt.rst | 23 Another option available through the GATT command is initiating the MTU exchange. To do it, use the
24 :code:`gatt exchange-mtu` command. To update the shell maximum MTU, you need to update Kconfig
|
| /Zephyr-latest/samples/bluetooth/mtu_update/ |
| D | README.rst | 5 Configure and exchange MTU between two devices.
30 This sample demonstrates the exchange of MTU between two devices to allow a
37 will exchange their MTUs and choose the minimum of the two. Thus the two MTU can
82 and send his MTU to the other device. If the MTU exchange succeeds, the central
99 mtu_exchange_cb: MTU exchange successful (247)
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | trickle.rst | 17 low-power and lossy networks) to exchange information in a highly
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | mailboxes.rst | 30 A mailbox allows threads, but not ISRs, to exchange messages.
37 allowing both threads participating in an exchange to know
47 a message exchange between compatible sending and receiving threads.
48 The mailbox also updates certain message descriptor fields during the exchange,
89 The exchange will not occur if thread B tries to receive a message
97 In a synchronous exchange, the sending thread blocks until the message
98 has been fully processed by the receiving thread. In an asynchronous exchange,
103 The technique used for a given message exchange is determined
106 The synchronous exchange technique provides an implicit form of flow control,
108 consumed by receiving threads. The asynchronous exchange technique provides an
[all …]
|
| /Zephyr-latest/samples/bluetooth/peripheral_nus/ |
| D | README.rst | 11 endpoint to exchange data. In this case, the sample assumes the data is UTF-8 encoded,
|
| /Zephyr-latest/drivers/can/ |
| D | Kconfig.xmc4xxx | 36 message exchange between MCU CAN devices without any external connectors.
|
| /Zephyr-latest/samples/subsys/canbus/isotp/ |
| D | README.rst | 5 Use ISO-TP library to exchange messages between two boards.
|
| /Zephyr-latest/samples/drivers/espi/ |
| D | README.rst | 5 Use eSPI to connect to a slave device and exchange virtual wire packets.
|
| /Zephyr-latest/samples/bluetooth/encrypted_advertising/ |
| D | README.rst | 12 - the exchange of the session key and the initialization vector using the Key
|
| /Zephyr-latest/modules/mbedtls/ |
| D | Kconfig.tls-generic | 45 comment "Supported key exchange modes"
79 PSK key exchange is used.
119 bool "TLS 1.3 PSK key exchange mode"
122 bool "TLS 1.3 ephemeral key exchange mode"
125 bool "TLS 1.3 PSK ephemeral key exchange mode"
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | gmap.rst | 54 uart:~$ gatt exchange-mtu
|
| D | bap.rst | 102 uart:~$ gatt exchange-mtu
116 uart:~$ gatt exchange-mtu
329 Use command :code:`gatt exchange-mtu` to make sure the MTU is configured
334 uart:~$ gatt exchange-mtu
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | networking_with_host.rst | 21 exchange data with the host system like a Linux desktop computer.
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | Kconfig.gatt | 205 bool "Automatically send ATT MTU exchange request on connect"
209 MTU exchange.
|
| /Zephyr-latest/doc/services/ipc/ipc_service/backends/ |
| D | ipc_service_icbmsg.rst | 47 …Ensure that the memory regions used for data exchange are unique (not overlapping any other region…
319 * To make sure that two sides are ready to exchange messages over that endpoint.
374 There is a binding of two endpoints and one fully processed data message exchange.
|
| D | ipc_service_icmsg.rst | 31 of an instance. Ensure that the memory regions used for data exchange are
|
| /Zephyr-latest/subsys/lorawan/services/ |
| D | Kconfig | 167 for multicast session key exchange and setting up a class C session.
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.smp | 89 O(N) in the number of CPUs, and in exchange reduces the number of
|
| /Zephyr-latest/boards/udoo/udoo_neo_full/doc/ |
| D | index.rst | 229 an exchange of information between this utility and the program running on the
301 to not exchange the information with the M4 core application using shared
|
| /Zephyr-latest/boards/adi/eval_adin2111ebz/doc/ |
| D | index.rst | 29 the 2 PHYs configuration and data exchange between SPI host and ports.
|
| /Zephyr-latest/samples/drivers/virtualization/ivshmem/doorbell/ |
| D | README.rst | 5 Use Inter-VM Shared Memory to exchange messages between two processes running on different
|
12
