Lines Matching refs:send
118 internal queues to sequence messages and send them in order to the FW.
136 The transport layer uses them to send and receive messages.
160 Once connection is established, peers send each other flow control bus messages
161 independently. Every peer may send a message only if it has received a
162 flow-control credit before. Once it sent a message, it may not send another one
164 Either side can send disconnect request bus message to end communication. Also
174 ISHTP client from either host or FW side wants to send something, it decides
175 whether to send over IPC or over DMA; for each transfer the decision is
184 if thw host doesn't support DMA, then it won't send DMA allocation, so FW can't
185 send DMA; if FW doesn't support DMA then it won't respond with
195 needs not wait for previous DMA_XFER to be ack'ed, and may send another message
199 Currently, ISH FW decides to send over DMA if ISHTP message is more than 3 IPC
206 TX and RX buffers respectively. On send request from client, the data to be
207 sent is copied to one of the send ring buffer and scheduled to be sent using
210 to send. Same thing holds true on receive side and flow control is required.