Home
last modified time | relevance | path

Searched refs:sending (Results 76 – 100 of 141) sorted by relevance

123456

/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dblob_srv.rst91 The BLOB Transfer Client sending the transfer must support transfer recovery for the transfer to
Ddfu.rst307 check and prepares their BLOB Transfer Server model for the transfer, before sending a status
329 the Distributor will stop sending any messages to Target nodes. When the firmware distribution is
330 resumed, the Distributor will continue sending the firmware from the last successfully transferred
363 Distributor starts the cancelling procedure by sending a cancelling message to all Target nodes. The
Dprovisioning.rst74 The provisioner initiates the Provisioning process by sending a Provisioning
Dblob.rst7 Transfer Model specification version 1.0 and provide functionality for sending large binary objects
/Zephyr-latest/tests/bsim/bluetooth/mesh/
DREADME.rst83 mesh initialization, as well as message sending and receiving.
/Zephyr-latest/subsys/net/l2/wifi/
DKconfig110 will prevent the AP from sending null data frames to the stations after
/Zephyr-latest/drivers/console/
DKconfig172 Enable the sending side of IPM console
203 where characters are stored before sending the whole line.
/Zephyr-latest/subsys/bluetooth/mesh/
DKconfig63 Use legacy advertising commands for mesh sending. Legacy
135 When this option is enabled, the latency of sending mesh messages
137 reduced reliability for sending mesh messages.
184 and the main advertising set is not busy with sending local
187 advertising sets, which is helpful for the sending of dense
222 Number of advertising buffers available for sending local messages.
592 hex "Interval between sending two consecutive segments"
596 This value controls the interval between sending two consecutive
1468 This option enables support for sending Solicitation PDUs.
1671 sending a request and listening for a response. This delay
[all …]
/Zephyr-latest/doc/kernel/memory_management/
Dslabs.rst140 Use memory slab blocks when sending large amounts of data from one thread
/Zephyr-latest/doc/kernel/services/data_passing/
Dpipes.rst206 Pipes are useful for sending streams of data between threads. Typical
/Zephyr-latest/subsys/net/ip/
DKconfig.ipv668 limit value is 0. When sending, the packet is dropped before
78 limit value is 0. When sending, the packet is dropped before
/Zephyr-latest/drivers/espi/
DKconfig76 completed by sending a virtual wire message to the eSPI master.
/Zephyr-latest/subsys/mgmt/osdp/
DKconfig.pd30 the message is directed, or the address of the PD sending the reply.
/Zephyr-latest/drivers/modem/
DKconfig176 sending a command to the modem UART.
/Zephyr-latest/subsys/net/lib/sockets/
DKconfig168 freed only when connection is gracefully closed by peer sending TLS
295 while sending. While receiving, packets (including all the headers)
/Zephyr-latest/subsys/net/lib/coap/
DKconfig108 This option enables the API for CoAP-client for sending CoAP requests
/Zephyr-latest/subsys/tracing/
DKconfig350 and sending.
/Zephyr-latest/drivers/net/
DKconfig79 cannot use the PPP connection to sending packets as that would
/Zephyr-latest/subsys/mgmt/mcumgr/grp/os_mgmt/
DKconfig128 as it will prevent sending zeroed stack information just to fill
/Zephyr-latest/subsys/net/lib/http/
DKconfig151 (i. e. not sending or receiving any data) before the server drops the
/Zephyr-latest/subsys/bluetooth/common/
DKconfig25 The Host supports sending of larger L2CAP PDUs than the ACL size and
271 sending vendor commands to controller which may interpret them in
/Zephyr-latest/doc/connectivity/bluetooth/shell/audio/
Dtbs.rst36 the client may subscribe and use either when sending requests if
/Zephyr-latest/doc/services/pm/
Ddevice_runtime.rst107 situation will not be the same if suspension involves sending packets through a
/Zephyr-latest/samples/net/sockets/http_server/
DREADME.rst219 sending requests to our server. Once we've collected enough data, we can
/Zephyr-latest/doc/services/zbus/
Dindex.rst45 * :dfn:`Virtual Distributed Event Dispatcher` (VDED), the bus logic responsible for sending
96 sending notifications from channel ``C3``. In (d), the event dispatcher will stop sending
884 * :zephyr:code-sample:`zbus-uart-bridge` shows an example of sending the operation of the channel to

123456