Searched refs:sending (Results 1 – 25 of 135) sorted by relevance
123456
| /Zephyr-latest/samples/drivers/ipm/ipm_esp32/ |
| D | README.rst | 43 PRO_CPU is sending a request, waiting remote response...
45 PRO_CPU is sending a request, waiting remote response...
47 PRO_CPU is sending a request, waiting remote response...
49 PRO_CPU is sending a request, waiting remote response...
51 PRO_CPU is sending a request, waiting remote response...
53 PRO_CPU is sending a request, waiting remote response...
55 PRO_CPU is sending a request, waiting remote response...
57 PRO_CPU is sending a request, waiting remote response...
|
| /Zephyr-latest/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.
|
| /Zephyr-latest/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 …]
|
| /Zephyr-latest/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-latest/subsys/sd/ |
| D | Kconfig | 84 int "Number of times to retry sending command to card"
87 Number of times to retry sending command to SD card in case of failure
90 int "Number of times to retry sending data to card"
93 Number of times to retry sending data to SD card in case of failure
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | network_tracing.rst | 14 are enabled. The system will start to collect the receiving and sending call
16 It will also collect packet sending or receiving timings i.e., how long
|
| 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-latest/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-latest/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-latest/drivers/mipi_dbi/ |
| D | Kconfig.nxp_lcdic | 19 Use DMA for transfers when sending data with the LCDIC driver.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | brg_cfg.rst | 71 feature on a node by sending a **Subnet Bridge Set** message to the Bridge Configuration
77 The Bridge Configuration Client can add or remove an entry from the Bridging Table by sending a
91 The Bridge Configuration Client can retrieve this information by sending a **Subnet Bridge Get**
95 entries from a Bridging Table by sending a **Bridging Table Get** message to the target node using
98 The Client can get a list of subnets currently bridged by a Subnet Bridge by sending a
103 store. The Client can retrieve this information by sending a **Bridging Table Size Get** message
|
| /Zephyr-latest/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-latest/subsys/net/lib/mqtt_sn/ |
| D | Kconfig | 81 int "Max time (seconds) to wait before sending SEARCHGW"
86 int "Max time (seconds) to wait before sending GWINFO"
|
| /Zephyr-latest/samples/subsys/zbus/benchmark/ |
| D | README.rst | 5 Measure the time for sending 256KB from a producer to N consumers.
7 This sample implements an application to measure the time for sending 256KB from the producer to the
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig.altera | 23 Enabling this will cause the transmitter to wait for rising edge of CTS before sending.
|
| /Zephyr-latest/drivers/lora/ |
| D | Kconfig.rylrxxx | 37 …mber of milliseconds before timing out when waiting for acknowledgment from radio after sending cmd
|
| /Zephyr-latest/drivers/i3c/ |
| D | Kconfig.stm32 | 33 during a single transfer. 2KB guarantees enough heap size for sending 256
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig.stack | 14 TX thread for sending network packets destined to it.
|
| /Zephyr-latest/subsys/mgmt/osdp/ |
| D | Kconfig | 63 bool "Skip sending the initial marking byte (0xFF)"
69 completely disable sending/expecting a mark byte to work with
|
| /Zephyr-latest/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-latest/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-latest/doc/connectivity/bluetooth/shell/host/ |
| D | iso.rst | 55 ISO sending...
|
| /Zephyr-latest/doc/connectivity/usb/device/api/ |
| D | usb_device.rst | 15 sending another packet the class driver should wait for the completion of
|
| /Zephyr-latest/samples/net/sockets/net_mgmt/ |
| D | README.rst | 11 for network management events that the networking subsystem is sending.
|
| /Zephyr-latest/samples/subsys/usb/uac2_explicit_feedback/ |
| D | README.rst | 27 The host achieves the average by sending either nominal or nominal ±1 sample
31 feedback code available, returns a feedback value that results in host sending
|
123456
