Skip to content

Latest commit

 

History

History
67 lines (53 loc) · 2.32 KB

ne-usbscan-pipe_type.md

File metadata and controls

67 lines (53 loc) · 2.32 KB
UID title description old-location tech.root ms.date keywords ms.keywords req.header req.include-header req.target-type req.target-min-winverclnt req.target-min-winversvr req.kmdf-ver req.umdf-ver req.ddi-compliance req.unicode-ansi req.idl req.max-support req.namespace req.assembly req.type-library req.lib req.dll req.irql targetos req.typenames f1_keywords topic_type api_type api_location api_name
NE:usbscan.PIPE_TYPE
PIPE_TYPE (usbscan.h)
The PIPE_TYPE data type is used as input to the DeviceIoControl function, if the I/O control code is IOCTL_CANCEL_IO or IOCTL_RESET_PIPE.
image\pipe_type.htm
image
05/03/2018
PIPE_TYPE enumeration
ALL_PIPE, EVENT_PIPE, PIPE_TYPE, PIPE_TYPE enumeration [Imaging Devices], READ_DATA_PIPE, WRITE_DATA_PIPE, image.pipe_type, stifnc_dd4122fa-8df4-4190-91ec-248a1e63ab64.xml, usbscan/ALL_PIPE, usbscan/EVENT_PIPE, usbscan/PIPE_TYPE, usbscan/READ_DATA_PIPE, usbscan/WRITE_DATA_PIPE
usbscan.h
Usbscan.h
Windows
Windows
PIPE_TYPE
PIPE_TYPE
usbscan/PIPE_TYPE
APIRef
kbSyntax
HeaderDef
usbscan.h
PIPE_TYPE

PIPE_TYPE enumeration

-description

The PIPE_TYPE data type is used as input to the DeviceIoControl function, if the I/O control code is IOCTL_CANCEL_IO or IOCTL_RESET_PIPE. An interrupt pipe, a bulk IN pipe, and a bulk OUT pipe are associated with each device handle supplied to DeviceIoControl. The specified PIPE_TYPE value indicates on which of these pipes the operation should be performed, as indicated in the following table.

-enum-fields

-field EVENT_PIPE

The operation should be performed on the interrupt pipe.

-field READ_DATA_PIPE

The operation should be performed on the bulk IN pipe.

-field WRITE_DATA_PIPE

The operation should be performed on the bulk OUT pipe.

-field ALL_PIPE

The operation should be performed on all transfer pipes (not just the pipes associated with the device handle supplied to DeviceIoControl).