Lines Matching refs:send
129 internal queues to sequence messages and send them in order to the FW.
148 The transport layer uses them to send and receive messages.
176 Once connection is established, peers send each other flow control bus messages
177 independently. Every peer may send a message only if it has received a
178 flow-control credit before. Once it sent a message, it may not send another one
180 Either side can send disconnect request bus message to end communication. Also
191 ISHTP client from either host or FW side wants to send something, it decides
192 whether to send over IPC or over DMA; for each transfer the decision is
201 if thw host doesn't support DMA, then it won't send DMA allocation, so FW can't
202 send DMA; if FW doesn't support DMA then it won't respond with
212 needs not wait for previous DMA_XFER to be ack'ed, and may send another message
216 Currently, ISH FW decides to send over DMA if ISHTP message is more than 3 IPC
224 TX and RX buffers respectively. On send request from client, the data to be
225 sent is copied to one of the send ring buffer and scheduled to be sent using
228 to send. Same thing holds true on receive side and flow control is required.