Home
last modified time | relevance | path

Searched refs:sending (Results 26 – 50 of 141) sorted by relevance

123456

/Zephyr-latest/samples/net/sockets/net_mgmt/
DREADME.rst11 for network management events that the networking subsystem is sending.
/Zephyr-latest/samples/net/sockets/txtime/
DKconfig9 string "Peer IP address we are sending packets to"
57 This tells what is the expected sending time of the network
/Zephyr-latest/subsys/bluetooth/host/
DKconfig.gatt22 These buffers are only used for sending anything over ATT.
95 bt_conn_set_security() to re-establish security prior to sending any
174 When enabled, this option will make the server block sending
209 This option if enabled allows automatically sending request for ATT
217 This option if enabled allows automatically sending request for connection
/Zephyr-latest/subsys/bluetooth/audio/
DKconfig28 int "Delay for notification sending retried attempt in 1.25 ms units"
/Zephyr-latest/samples/drivers/uart/echo_bot/
DREADME.rst14 The polling API is used for sending data and the interrupt-driven API
/Zephyr-latest/doc/hardware/peripherals/
Dgnss.rst21 subsystem covers everything from sending and receiving commands
/Zephyr-latest/samples/subsys/usb/uac2_explicit_feedback/
DREADME.rst33 The host achieves the average by sending either nominal or nominal ±1 sample
37 feedback code available, returns a feedback value that results in host sending
/Zephyr-latest/doc/kernel/services/data_passing/
Dmessage_queues.rst32 The data item pointed at by the sending thread is copied to a waiting thread,
38 the sending thread may choose to wait for space to become available.
39 Any number of sending threads may wait simultaneously when the ring buffer
41 it is given to the highest priority sending thread that has waited the longest.
/Zephyr-latest/subsys/modem/backends/
DKconfig32 when receiving a byte before sending the RECEIVE_READY pipe event.
/Zephyr-latest/samples/subsys/canbus/isotp/
DREADME.rst39 Start sending data
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dblob_cli.rst7 sending BLOBs of any size to any number of Target nodes, in both Push BLOB Transfer Mode and Pull
69 BLOB Transfer Client sends each message to all Target nodes at the same time. However, sending
71 sending them to unicast addresses, as there is no transport layer acknowledgment mechanism for
Dpriv_beacon_srv.rst18 must be instantiated for the device to support sending of the private beacons,
/Zephyr-latest/samples/boards/renesas/openamp_linux_zephyr/
DREADME.rst140 [CM33] sending payload number 0 of size 17
142 [CM33] sending payload number 1 of size 18
147 [CM33] sending payload number 471 of size 488
/Zephyr-latest/samples/subsys/zbus/remote_mock/
DREADME.rst50 D: sending message to host (channel sensor_data)
53 D: sending sensor data err = 0
/Zephyr-latest/doc/connectivity/networking/api/
Dcoap_client.rst23 The following is an example of a CoAP client initialization and request sending:
78 LOG_ERR("Error in sending request %d", code);
Dnet_l2.rst55 error code if there was a failure sending the network packet.
84 receiving or sending a network packet. The rest is hardware dependent
100 On sending, the device driver send function will be called, and it is up to
141 encrypted and otherwise pre-processed fragment buffers, sending one buffer
/Zephyr-latest/subsys/bluetooth/mesh/
Dblob_cli.c96 cli->tx.sending = 0; in cli_state_reset()
385 cli->tx.sending = 1U; in send()
413 if (!cli->tx.ctx.is_inited || !cli->tx.sending) { in tx_complete()
417 cli->tx.sending = 0U; in tx_complete()
492 __ASSERT(!cli->tx.sending, "still sending"); in retry_timeout()
517 if (cli->tx.ctx.is_inited || cli->tx.sending) { in blob_cli_broadcast()
557 if (!--cli->tx.pending && !cli->tx.sending) { in blob_cli_broadcast_rsp()
1189 if (!cli->tx.sending) { in rx_block_status()
1577 cli->tx.sending = 0; in bt_mesh_blob_cli_suspend()
/Zephyr-latest/include/zephyr/bluetooth/mesh/
Dblob_cli.h309 uint8_t sending : 1, member
/Zephyr-latest/subsys/usb/device/class/
DKconfig.cdc44 Time in milliseconds to wait before sending actual payload to host.
/Zephyr-latest/doc/connectivity/networking/
Dnet_config_guide.rst62 How many network buffers are allocated for sending data. This is similar setting
63 as the receive buffer count but for sending.
79 5-tuple that is used when listening or sending network traffic. Each BSD socket in the
196 Maximum sending window size to use.
197 This value affects how the TCP selects the maximum sending window
231 or sending network data. Each traffic class queue is implemented as a thread
/Zephyr-latest/doc/connectivity/bluetooth/api/
Dl2cap.rst24 For sending data the :c:func:`bt_l2cap_chan_send` API can be used noting that
/Zephyr-latest/doc/connectivity/canbus/
Disotp.rst35 The FC also defines the conditions of sending, namely the block-size (BS) and
/Zephyr-latest/drivers/bluetooth/hci/
DKconfig.nxp12 Enabling this feature will allow to save power at the cost of some latency when sending a HCI
/Zephyr-latest/subsys/net/l2/ethernet/
DKconfig23 net_buf when sending data. The default is still to have layer 2
105 int "Time interval (in seconds) between sending gratuitous ARP requests"
/Zephyr-latest/doc/services/device_mgmt/
Dec_host_cmd.rst23 sending and receiving commands via chosen peripheral.
41 sends/receives specific number of bytes) and need to constant sending status byte (the SPI module

123456