Searched refs:sending (Results 1 – 25 of 110) sorted by relevance
12345
| /Zephyr-Core-3.5.0/samples/drivers/ipm/ipm_esp32/ |
| D | README.rst | 42 PRO_CPU is sending a fake request, waiting remote response...
44 PRO_CPU is sending a fake request, waiting remote response...
46 PRO_CPU is sending a fake request, waiting remote response...
48 PRO_CPU is sending a fake request, waiting remote response...
50 PRO_CPU is sending a fake request, waiting remote response...
52 PRO_CPU is sending a fake request, waiting remote response...
54 PRO_CPU is sending a fake request, waiting remote response...
|
| /Zephyr-Core-3.5.0/doc/connectivity/networking/api/ |
| D | net_core.rst | 13 The network subsystem contains two functions for sending and receiving
19 For sending, the ``net_send_data()`` can be used. Typically applications do not
21 for sending and receiving network data.
|
| D | coap_client.rst | 22 The following is an example of a CoAP client initialization and request sending:
77 LOG_ERR("Error in sending request %d", code);
|
| /Zephyr-Core-3.5.0/doc/kernel/services/data_passing/ |
| D | mailboxes.rst | 31 A thread that sends a message is known as the **sending thread**,
45 Both the sending thread and the receiving thread supply a message descriptor
47 a message exchange between compatible sending and receiving threads.
69 it is given to a mailbox by the sending thread. The message is then owned
78 A sending thread can specify the address of the thread to which the message
83 A message is exchanged only when the requirements of both the sending thread
97 In a synchronous exchange, the sending thread blocks until the message
99 the sending thread does not wait until the message has been received
100 by another thread before continuing; this allows the sending thread to do
104 by the sending thread.
[all …]
|
| D | message_queues.rst | 32 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-Core-3.5.0/subsys/canbus/isotp/ |
| D | Kconfig | 37 int "Ar and As timeout [ms] (sending and receiving timeout)"
56 (for classic CAN) and unused bytes must be padded by the sending
104 int "Number of data buffers for sending data"
116 for sending are allocated from.
124 This option enables buffered sending contexts. This makes send and
128 int "Amount of context buffers for sending data"
|
| /Zephyr-Core-3.5.0/subsys/ipc/ipc_service/backends/ |
| D | Kconfig.icmsg_me | 7 int "Size of sending buffer size"
11 Size of a static buffer used for preparring data to send in sending
|
| /Zephyr-Core-3.5.0/samples/subsys/zbus/uart_bridge/ |
| D | README.rst | 34 D: Core sending start measurement with status 0
37 D: Peripheral sending sensor data
47 D: Core sending start measurement with status 1
53 D: Peripheral sending sensor data
|
| /Zephyr-Core-3.5.0/doc/hardware/peripherals/ |
| D | sdhc.rst | 17 An SD host controller is a device capable of sending SD commands to an attached
32 Whether the provided buffer is used for sending or reading data depends on the
|
| /Zephyr-Core-3.5.0/samples/bluetooth/central_iso/ |
| D | README.rst | 13 starts sending data.
|
| /Zephyr-Core-3.5.0/samples/subsys/zbus/benchmark/ |
| D | README.rst | 5 Measure the time for sending 256KB from a producer to X consumers.
7 This sample implements an application to measure the time for sending 256KB from the producer to th…
|
| /Zephyr-Core-3.5.0/drivers/serial/ |
| D | Kconfig.altera | 23 Enabling this will cause the transmitter to wait for rising edge of CTS before sending.
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/host/ |
| D | Kconfig.gatt | 13 from sending new requests until a previous one has been responded
14 or sending a new indication until a previous one has been
89 bt_conn_set_security() to re-establish security prior to sending any
166 When enabled, this option will make the server block sending
201 This option if enabled allows automatically sending request for ATT
209 This option if enabled allows automatically sending request for connection
|
| /Zephyr-Core-3.5.0/doc/connectivity/networking/ |
| D | net-stack-architecture.rst | 57 * **L2 Network Technologies.** This provides a common API for sending and
69 physical sending or receiving of network packets.
127 Data sending (TX)
131 :ref:`BSD socket API <bsd_sockets_interface>` when sending the data.
133 2. The application data is prepared for sending to kernel space and then
|
| /Zephyr-Core-3.5.0/subsys/sd/ |
| D | Kconfig | 82 int "Number of times to retry sending data to card"
85 Number of times to retry sending data to SD card in case of failure
|
| /Zephyr-Core-3.5.0/subsys/net/ip/ |
| D | Kconfig.stack | 14 TX thread for sending network packets destined to it.
|
| /Zephyr-Core-3.5.0/samples/drivers/ipm/ipm_imx/ |
| D | README.rst | 12 the received data is printed to the console. When sending the data back,
23 and blocking sending of the data back is done in the interrupt handler, which
|
| /Zephyr-Core-3.5.0/subsys/mgmt/osdp/ |
| D | Kconfig | 62 bool "Skip sending the initial marking byte (0xFF)"
68 completely disable sending/expecting a mark byte to work with
|
| /Zephyr-Core-3.5.0/samples/net/sockets/net_mgmt/ |
| D | README.rst | 11 for network management events that the networking subsystem is sending.
|
| /Zephyr-Core-3.5.0/samples/drivers/uart/echo_bot/ |
| D | README.rst | 14 The polling API is used for sending data and the interrupt-driven API
|
| /Zephyr-Core-3.5.0/subsys/mgmt/mcumgr/smp_client/ |
| D | Kconfig | 29 The time (in ms) which the SMP client will wait for a response before re-sending
|
| /Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/shell/ |
| D | iso.rst | 55 ISO sending...
|
| /Zephyr-Core-3.5.0/doc/connectivity/usb/device/api/ |
| D | usb_device.rst | 15 sending another packet the class driver should wait for the completion of
|
| /Zephyr-Core-3.5.0/samples/net/sockets/txtime/ |
| D | Kconfig | 9 string "Peer IP address we are sending packets to"
57 This tells what is the expected sending time of the network
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/mesh/ |
| D | blob_cli.c | 98 cli->tx.sending = 0; in cli_state_reset()
387 cli->tx.sending = 1U; in send()
415 if (!cli->tx.ctx.is_inited || !cli->tx.sending) { in tx_complete()
419 cli->tx.sending = 0U; in tx_complete()
494 __ASSERT(!cli->tx.sending, "still sending"); in retry_timeout()
519 if (cli->tx.ctx.is_inited || cli->tx.sending) { in blob_cli_broadcast()
559 if (!--cli->tx.pending && !cli->tx.sending) { in blob_cli_broadcast_rsp()
1190 if (!cli->tx.sending) { in rx_block_status()
1577 cli->tx.sending = 0; in bt_mesh_blob_cli_suspend()
|
12345
