Important: |
---|
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
This function initiates an interrupt transfer with a USB device.
USB_TRANSFER IssueInterruptTransfer( USB_PIPE hPipe , LPTRANSFER_NOTIFY_ROUTINE lpStartAddress , LPVOID lpvNotifyParameter , DWORD dwFlags , DWORD dwBufferSize , LPVOID lpvBuffer , ULONG uBufferPhysicalAddress );
Parameters
Return Values
A USB_TRANSFER handle indicates success. NULL indicates failure. IssueInterruptTransferbehaves either synchronously or asynchronously, depending on the value you provide for lpStartAddressand whether dwFlagscontains the USB_NO_WAIT flag, as shown in the following table:
lpStartAddress | dwFlags| USB_NO_WAIT | Behavior |
---|---|---|
NULL | 0 | Synchronous |
NULL | USB_NO_WAIT | Asynchronous |
non-NULL | 0 | Asynchronous |
non-NULL | USB_NO_WAIT | Asynchronous |
When behaving asynchronously, the function will invoke your callback function, if one is specified in lpStartAddress, when the transfer is complete.
Remarks
This function initiates an interrupt transfer to a USB device on the specified endpoint.
Requirements
Runs on | Versions | Defined in | Include | Link to |
---|---|---|---|---|
Windows CE OS | 2.10 and later |
Note This API is part of the complete Windows CE OS package as provided by Microsoft. The functionality of a particular platform is determined by the original equipment manufacturer (OEM) and some devices may not support this API.
See Also
AbortTransfer, GetTransferStatus, IsTransferComplete
Last updated on Tuesday, July 13, 2004