LPISSUE_INTERRUPT_TRANSFER (Windows CE 5.0)
This function initiates an interrupt transfer with a universal serial bus (USB) device on the specified endpoint.
typedef USB_TRANSFER (* LPISSUE_INTERRUPT_TRANSFER)( USB_PIPE hPipe, LPTRANSFER_NOTIFY_ROUTINE lpStartAddress, LPVOID lpvNotifyParameter, DWORD dwFlags, DWORD dwBufferSize, LPVOID lpvBuffer, ULONG uBufferPhysicalAddress);
Parameters
- hPipe
[in] Handle to an open USB pipe. - lpStartAddress
[in] Pointer to the address of a callback routine of type LPTRANSFER_NOTIFY_ROUTINE, or NULL if no callback routine is necessary - lpvNotifyParameter
[in] Parameter to pass to the callback routine. - dwFlags
[in] Flags for the transfer. These flags shown in the following list are declared in the Usbtypes.h header file.- USB_IN_TRANSFER
- USB_OUT_TRANSFER
- USB_NO_WAIT
- USB_SHORT_TRANSFER_OK
- USB_START_ISOCH_ASAP
- USB_COMPRESS_ISOCH
- USB_SEND_TO_DEVICE
- USB_SEND_TO_INTERFACE
- USB_SEND_TO_ENDPOINT
- USB_DONT_BLOCK_FOR_MEM
- dwBufferSize
[in] Size of data buffer. - lpvBuffer
[in] Pointer to the data buffer. If the physical buffer address is specified, this must contain the virtual address of the buffer. - uBufferPhysicalAddress
[in] Physical address, which might be NULL, of the data buffer.
Return Values
A USB_TRANSFER handle indicates success. NULL indicates failure. IssueControlTransfer behaves either synchronously or asynchronously, depending on the value you provide for lpStartAddress and whether dwFlags contains the USB_NO_WAIT flag.
The following table shows the possible flags.
| 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, this function invokes the callback function optionally specified by lpStartAddress when the transfer is complete.
Requirements
OS Versions: Windows CE 2.10 and later.
Header: Usbdi.h.
See Also
Send Feedback on this topic to the authors