Lines Matching full:transfer
42 /// USB data transfer direction
51 // USB Transfer Results
65 Async USB transfer callback routine.
67 @param Data Data received or sent via the USB Asynchronous Transfer, if the
68 transfer completed successfully.
70 Transfer, if transfer successfully completes.
72 @param Status Indicates the result of the asynchronous transfer.
74 …@retval EFI_SUCCESS The asynchronous USB transfer request has been successfully executed.
75 @retval EFI_DEVICE_ERROR The asynchronous USB transfer request failed.
92 This function is used to manage a USB device with a control transfer pipe. A control transfer is
99 @param Timeout Indicating the transfer should be completed within this time frame.
104 @param Status A pointer to the result of the USB transfer.
106 @retval EFI_SUCCESS The control transfer has been successfully executed.
107 @retval EFI_DEVICE_ERROR The transfer failed. The transfer status is returned in Status.
110 @retval EFI_TIMEOUT The control transfer fails due to timeout.
126 This function is used to manage a USB device with the bulk transfer pipe. Bulk Transfers are
127 typically used to transfer large amounts of data to/from USB devices.
143 @param Timeout Indicating the transfer should be completed within this time frame.
147 @param Status This parameter indicates the USB transfer status.
149 @retval EFI_SUCCESS The bulk transfer has been successfully executed.
150 @retval EFI_DEVICE_ERROR The transfer failed. The transfer status is returned in Status.
153 @retval EFI_TIMEOUT The control transfer fails due to timeout.
168 This function is used to manage a USB device with an interrupt transfer pipe. An Asynchronous
169 Interrupt Transfer is typically used to query a device's status at a fixed rate. For example,
170 keyboard, mouse, and hub devices use this type of transfer to query their interrupt endpoints at
182 @param IsNewTransfer If TRUE, a new transfer will be submitted to USB controller. If
183 FALSE, the interrupt transfer is deleted from the device's interrupt
184 transfer queue.
185 …@param PollingInterval Indicates the periodic rate, in milliseconds, that the transfer is t…
192 interrupt transfer is completed. This parameter is required
197 …@retval EFI_SUCCESS The asynchronous USB transfer request transfer has been successfully…
198 @retval EFI_DEVICE_ERROR The asynchronous USB transfer request failed.
214 This function is used to manage a USB device with an interrupt transfer pipe.
229 @param Timeout The time out, in seconds, for this transfer. If Timeout is 0,
232 … transfer is not completed in this time frame, then EFI_TIMEOUT is returned.
233 @param Status This parameter indicates the USB transfer status.
235 @retval EFI_SUCCESS The sync interrupt transfer has been successfully executed.
237 @retval EFI_DEVICE_ERROR The sync interrupt transfer request failed.
239 @retval EFI_TIMEOUT The transfer fails due to timeout.
253 This function is used to manage a USB device with an isochronous transfer pipe. An Isochronous
254 transfer is typically used to transfer streaming data.
268 @param Status This parameter indicates the USB transfer status.
270 @retval EFI_SUCCESS The isochronous transfer has been successfully executed.
272 …@retval EFI_DEVICE_ERROR The transfer failed due to the reason other than timeout, The error …
275 @retval EFI_TIMEOUT The transfer fails due to timeout.
288 This function is used to manage a USB device with an isochronous transfer pipe. An Isochronous
289 transfer is typically used to transfer streaming data.
305 called if the requested isochronous transfer is completed.
308 …@retval EFI_SUCCESS The asynchronous isochronous transfer has been successfully submitted
471 /// in the USB 1.1 Specification. These include control transfer, interrupt
472 /// transfer, bulk transfer and isochronous transfer. The EFI_USB_IO_PROTOCOL
478 // IO transfer