Searched refs:receive (Results 1 – 25 of 163) sorted by relevance
1234567
| /Zephyr-Core-3.5.0/drivers/ethernet/ |
| D | Kconfig.esp32 | 16 int "ESP32 Ethernet receive thread stack size"
20 int "ESP32 Ethernet receive thread priority"
|
| /Zephyr-Core-3.5.0/drivers/serial/ |
| D | Kconfig.nxp_s32 | 23 int "The maximum duration to receive a byte data in blocking mode"
26 Maximum duration in micro-seconds to receive a byte data in blocking mode.
|
| D | Kconfig.xmc4xxx | 24 if there is data in the receive fifo. Otherwise, an interrupt will
25 trigger only once on the first received byte. The receive fifo will
|
| D | Kconfig.altera | 22 Before enabling this, please try to optimise the ISR to fetch the receive data faster.
|
| /Zephyr-Core-3.5.0/subsys/mgmt/mcumgr/transport/ |
| D | Kconfig.dummy | 22 int "Size of receive buffer for dummy interface mcumgr fragments"
25 Specifies the size of the mcumgr dummy backend receive buffer,
|
| /Zephyr-Core-3.5.0/doc/kernel/services/data_passing/ |
| D | mailboxes.rst | 8 A mailbox allows threads to send and receive messages of any size
25 * A **receive queue** of threads that are waiting to receive a message.
81 it wishes to receive a message, or it can receive a message from any thread
87 it will be received by thread B if thread B tries to receive a message
88 from thread A or if thread B tries to receive from any thread.
89 The exchange will not occur if thread B tries to receive a message
91 even if it tries to receive a message from thread A (or from any thread).
166 to allow any thread to receive the message. Leave this field uninitialized
172 to receive a message sent by any thread. Leave this field uninitialized
305 characterizes the message it wants to receive. It then calls one of the
[all …]
|
| /Zephyr-Core-3.5.0/tests/bsim/bluetooth/ll/bis/tests_scripts/ |
| D | broadcast_iso.sh | 16 -v=${verbosity_level} -s=${simulation_id} -d=0 -testid=receive
|
| D | broadcast_iso_ticker_expire_info.sh | 16 -v=${verbosity_level} -s=${simulation_id} -d=0 -testid=receive
|
| /Zephyr-Core-3.5.0/soc/xtensa/espressif_esp32/esp32_net/ |
| D | Kconfig.soc | 36 all four interfaces (WiFi station, WiFi softap, Bluetooth and Ethernet) receive a universally
39 only two interfaces (WiFi station and Bluetooth) receive a universally administered MAC address.
41 The remaining two interfaces (WiFi softap and Ethernet) receive local MAC addresses.
|
| /Zephyr-Core-3.5.0/subsys/ipc/ipc_service/backends/ |
| D | Kconfig.icmsg_me | 32 bool "Nocopy feature for receive path"
35 Enable nocopy feature for receive path of multiendpoint icmsg
|
| /Zephyr-Core-3.5.0/samples/net/sockets/can/ |
| D | README.rst | 5 Send and receive raw CAN frames using BSD sockets API.
17 application can receive CAN frames.
|
| /Zephyr-Core-3.5.0/doc/connectivity/networking/ |
| D | net_pkt_processing_stats.rst | 16 :kconfig:option:`CONFIG_NET_PKT_TXTIME_STATS` and for receive (RX) path the options is
37 transmit or receive queues defined in the system. These are controlled by
74 * Packet is about to be placed to receive queue. The time it took from network
76 * The correct RX thread is invoked, and the packet is read from the receive
|
| D | net-stack-architecture.rst | 35 connection, send or receive data, and close a connection. The application can
92 :ref:`k_fifo <fifos_v2>`). By default there is only one receive queue in
93 the system, but it is possible to have up to 8 receive queues.
95 See :ref:`traffic-class-support` for more details. The receive queues also
115 7. The application will then receive the data and can process it as needed.
118 that will receive the data.
|
| D | networking-api-usage.rst | 7 :zephyr_file:`include/zephyr/net/socket.h` to create a connection, send or receive data,
|
| /Zephyr-Core-3.5.0/soc/xtensa/intel_adsp/ace/ |
| D | Kconfig.soc | 23 DSP Communication Widget is a device for generic sideband message transmit/receive.
|
| /Zephyr-Core-3.5.0/drivers/i2c/ |
| D | Kconfig.ifx_xmc4 | 21 Buffer to receive data as an I2C Target.
|
| D | Kconfig.ifx_cat1 | 22 Buffer to receive data as an I2C Target.
|
| /Zephyr-Core-3.5.0/doc/connectivity/networking/api/ |
| D | promiscuous.rst | 16 to receive. This mode is normally used for packet sniffing as used
23 and to wait for and receive a network data to arrive. Not all network
|
| D | websocket.rst | 48 The Websocket socket can then be used to send or receive data, and the
51 BSD socket API functions can be used to send and receive application data.
|
| /Zephyr-Core-3.5.0/doc/services/input/ |
| D | index.rst | 33 to only receive events from a specific device. If there's no actual device
35 subscribers with no device filter will receive the event.
43 callback will receive all the events in the system. This is the only type of
|
| /Zephyr-Core-3.5.0/doc/kernel/services/ |
| D | index.rst | 57 … Data structure Data item size Data Alignment ISRs can receive? ISRs can send? …
74 [3] ISRs can receive only when passing K_NO_WAIT as the timeout
79 [5] ISRS can send and/or receive only when passing K_NO_WAIT as the
|
| /Zephyr-Core-3.5.0/include/zephyr/modem/ |
| D | pipe.h | 59 modem_pipe_api_receive receive; member
|
| /Zephyr-Core-3.5.0/modules/hal_nordic/ |
| D | Kconfig | 111 int "nRF 802.15.4 receive buffers"
114 Number of buffers in nRF 802.15.4 driver receive queue. If this value is modified,
198 int "nRF 802.15.4 receive buffers"
201 Number of buffers in nRF 802.15.4 driver serialization host's receive queue.
|
| /Zephyr-Core-3.5.0/samples/bluetooth/iso_receive/ |
| D | README.rst | 1 .. _bluetooth-iso-receive-sample:
|
| /Zephyr-Core-3.5.0/doc/hardware/peripherals/ |
| D | espi.rst | 10 based on SPI. It also features a four-wire interface (receive, transmit, clock
|
1234567
