Home
last modified time | relevance | path

Searched refs:receive (Results 1 – 25 of 547) sorted by relevance

12345678910>>...22

/linux-6.15/Documentation/infiniband/
H A Dtag_matching.rst14 The ordering rules require that when more than one pair of send and receive
16 and the earliest posted-receive is the pair that must be used to satisfy the
23 corresponding matching receive is posted. If a matching receive is posted,
45 unexpected message list. The application posts receive buffers through calls
46 to the MPI receive routines in the posted receive list and posts send messages
47 using the MPI send routines. The head of the posted receive list may be
50 When send is initiated and arrives at the receive side, if there is no
54 specified receive buffer. This allows overlapping receive-side MPI tag
58 the software unexpected message list for a matching receive. If a match is
63 pre-posted receive to this list, this receive is passed to the hardware.
[all …]
/linux-6.15/drivers/staging/greybus/
H A Dlog.c22 struct gb_log_send_log_request *receive; in gb_log_request_handler() local
31 if (op->request->payload_size < sizeof(*receive)) { in gb_log_request_handler()
33 op->request->payload_size, sizeof(*receive)); in gb_log_request_handler()
36 receive = op->request->payload; in gb_log_request_handler()
37 len = le16_to_cpu(receive->len); in gb_log_request_handler()
38 if (len != (op->request->payload_size - sizeof(*receive))) { in gb_log_request_handler()
40 (op->request->payload_size - sizeof(*receive))); in gb_log_request_handler()
54 receive->msg[len - 1] = '\0'; in gb_log_request_handler()
60 dev_dbg(dev, "%s", receive->msg); in gb_log_request_handler()
H A Draw.c97 struct gb_raw_send_request *receive; in gb_raw_request_handler() local
106 if (op->request->payload_size < sizeof(*receive)) { in gb_raw_request_handler()
108 op->request->payload_size, sizeof(*receive)); in gb_raw_request_handler()
111 receive = op->request->payload; in gb_raw_request_handler()
112 len = le32_to_cpu(receive->len); in gb_raw_request_handler()
123 return receive_data(raw, len, receive->data); in gb_raw_request_handler()
/linux-6.15/Documentation/devicetree/bindings/powerpc/fsl/
H A Dmpic-msgr.txt25 - mpic-msgr-receive-mask: Specifies what registers in the containing block
26 are allowed to receive interrupts. The value is a bit mask where a set
27 bit at bit 'n' indicates that message register 'n' can receive interrupts.
50 // Message registers 0 and 2 in this block can receive interrupts on
53 mpic-msgr-receive-mask = <0x5>;
59 // Message registers 0 and 2 in this block can receive interrupts on
62 mpic-msgr-receive-mask = <0x5>;
/linux-6.15/Documentation/networking/device_drivers/can/freescale/
H A Dflexcan.rst19 and i.MX53 SOCs) only receive RTR frames if the controller is
30 With the "rx-rtr" private flag the ability to receive RTR frames can
31 be waived at the expense of losing the ability to receive RTR
37 The CAN controller can and will receive RTR frames.
39 On some IP cores the controller cannot receive RTR frames in the
45 Waive ability to receive RTR frames. (not supported on all IP cores)
/linux-6.15/Documentation/networking/
H A Dstrparser.rst17 The strparser works in one of two modes: receive callback or general
20 In receive callback mode, the strparser is called from the data_ready
33 functions, and a data_ready function for receive callback mode. The
48 socket associated with the stream parser for use with receive
101 maximum messages size is the limit of the receive socket
156 processing a timeout). In receive callback mode the default
165 by the lock callback. In receive callback mode the default
197 the TCP socket in receive callback mode. The stream parser may
227 A timer is set when assembly starts for a new message. In receive
232 socket if in receive callback mode.
[all …]
H A Doa-tc6-framework.rst59 receive (RX) chunks. Chunks in both transmit and receive directions may
69 In parallel, receive data chunks are received on MISO. Each receive data
71 The data footer indicates if there is receive frame data present within
189 any receive frame data within the current chunk.
254 host will be sent as multiple receive data chunks. Each receive data
288 field is zero when there is no receive frame data
296 whether the current receive data chunk contains valid
347 SPI host will initiate the data receive transaction based on the receive
356 once the receive data chunks become available again for reading, the
367 data footer had no receive data chunks available and once the receive
[all …]
H A Dscaling.rst27 Contemporary NICs support multiple receive and transmit descriptor queues
31 of logical flows. Packets for each flow are steered to a separate receive
42 stores a queue number. The receive queue for a packet is determined
114 RSS should be enabled when latency is a concern or whenever receive
120 receive queue overflows due to a saturated CPU, because in default
204 Each receive hardware queue has an associated list of CPUs to which
221 can be configured for each receive queue using a sysfs file entry::
450 configured for each receive queue by the driver, so no additional
482 2. XPS using receive queues map
484 This mapping is used to pick transmit queue based on the receive
[all …]
H A Dtc-queue-filters.rst8 to a single queue on both the transmit and receive side.
22 Likewise, on the receive side, the two filters for selecting set of
31 receive queue. The action skbedit queue_mapping for receive queue
H A Dkcm.rst9 can efficiently send and receive application protocol messages over TCP using
47 Similarly, in the receive path, messages are constructed on each TCP socket
55 messages on receive as well as other connection specific information for KCM.
63 can be used to send and receive messages from the KCM socket.
98 KCM limits the maximum receive message size to be the size of the receive
189 Disabling receive on KCM socket
193 When receive is disabled, any pending messages in the socket's
194 receive buffer are moved to other sockets. This feature is useful
264 On receive, the KCM module attempts to queue messages received on the
266 changes at each receive ready callback on the KCM socket. The application
[all …]
H A Dmctp.rst11 The core code provides a socket-based interface to send and receive MCTP
83 Sockets that receive incoming request packets will bind to a local address,
100 The reference to 'incoming' is important here; a bound socket will only receive
111 receive incoming packets from any locally-connected network. A specific network
112 value will cause the socket to only receive incoming messages from that network.
115 ``MCTP_ADDR_ANY`` configures the socket to receive messages addressed to any
118 The ``smctp_type`` field specifies which message types to receive. Only the
173 Sockets will only receive responses to requests they have sent (with TO=1) and
176 ``recvfrom()``, ``recvmsg()``, ``recv()`` : receive an MCTP message
212 Like the send calls, sockets will only receive responses to requests they have
[all …]
/linux-6.15/drivers/input/serio/
H A Dlibps2.c267 unsigned int receive = (command >> 8) & 0xf; in __ps2_command() local
272 if (receive > sizeof(ps2dev->cmdbuf)) { in __ps2_command()
290 ps2dev->cmdcnt = receive; in __ps2_command()
312 if (receive) { in __ps2_command()
316 for (i = 0; i < receive; i++) in __ps2_command()
317 ps2dev->cmdbuf[(receive - 1) - i] = param[i]; in __ps2_command()
358 for (i = 0; i < receive; i++) in __ps2_command()
359 param[i] = ps2dev->cmdbuf[(receive - 1) - i]; in __ps2_command()
360 kmsan_unpoison_memory(param, receive); in __ps2_command()
379 receive, param ?: send_param); in __ps2_command()
/linux-6.15/tools/testing/selftests/net/packetdrill/
H A Dtcp_tcp_info_tcp-info-rwnd-limited.pkt14 // Server advertises 0 receive window.
30 // Server opens the receive window.
38 // Server advertises a very small receive window.
44 // Server opens the receive window again.
H A Dtcp_zerocopy_epoll_edge.pkt7 // fire two sends with MSG_ZEROCOPY and receive the acks. confirm that EPOLLERR
37 // receive only one EPOLLERR for the two sends above.
45 // receive only one EPOLLERR for the third send above.
H A Dtcp_zerocopy_epoll_exclusive.pkt8 // fire two sends with MSG_ZEROCOPY and receive the acks. confirm that EPOLLERR
39 // receive only one EPOLLERR for the two sends above.
47 // receive only one EPOLLERR for the third send above.
H A Dtcp_zerocopy_epoll_oneshot.pkt7 // fire two sends with MSG_ZEROCOPY and receive the acks. confirm that EPOLLERR
38 // receive only one EPOLLERR for the two sends above.
46 // receive no EPOLLERR for the third send above.
H A Dtcp_close_close-local-close-then-remote-fin.pkt3 // the local process calls close() first, so we send a FIN, and receive an ACK.
4 // Then we receive a FIN and ACK it.
/linux-6.15/Documentation/userspace-api/media/rc/
H A Dlirc-get-rec-mode.rst14 LIRC_GET_REC_MODE/LIRC_SET_REC_MODE - Get/set current receive mode.
34 Mode used for receive.
39 Get and set the current receive mode. Only
/linux-6.15/Documentation/devicetree/bindings/interrupt-controller/
H A Dcirrus,clps711x-intc.txt25 13: URXINT1 UART1 receive FIFO half full
29 17: SS2RX SSI2 receive FIFO half or greater full
32 29: URXINT2 UART2 receive FIFO half full
/linux-6.15/net/caif/
H A Dcfveil.c33 vei->layer.receive = cfvei_receive; in cfvei_create()
44 caif_assert(layr->receive != NULL); in cfvei_receive()
55 ret = layr->up->receive(layr->up, pkt); in cfvei_receive()
H A Dcfdgml.c34 dgm->layer.receive = cfdgml_receive; in cfdgml_create()
46 caif_assert(layr->receive != NULL); in cfdgml_receive()
61 ret = layr->up->receive(layr->up, pkt); in cfdgml_receive()
H A Dcfutill.c34 util->layer.receive = cfutill_receive; in cfutill_create()
46 caif_assert(layr->up->receive != NULL); in cfutill_receive()
56 return layr->up->receive(layr->up, pkt); in cfutill_receive()
H A Dcfdbgl.c27 dbg->layer.receive = cfdbgl_receive; in cfdbgl_create()
35 return layr->up->receive(layr->up, pkt); in cfdbgl_receive()
/linux-6.15/Documentation/devicetree/bindings/sound/
H A Dadi,axi-i2s.txt3 The core can be generated with transmit (playback), only receive
15 the core. The core expects two dma channels if both transmit and receive are
17 - dma-names : "tx" for the transmit channel, "rx" for the receive channel.
/linux-6.15/Documentation/devicetree/bindings/net/can/
H A Drenesas,rcar-canfd.yaml122 - description: CAN receive FIFO interrupt
125 - description: CAN0 transmit/receive FIFO receive completion interrupt
128 - description: CAN1 transmit/receive FIFO receive completion interrupt

12345678910>>...22