Skip to content

Latest commit

 

History

History
91 lines (66 loc) · 3.07 KB

nf-wdfusb-wdfusbinterfacegetnumconfiguredpipes.md

File metadata and controls

91 lines (66 loc) · 3.07 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
NF:wdfusb.WdfUsbInterfaceGetNumConfiguredPipes
WdfUsbInterfaceGetNumConfiguredPipes function (wdfusb.h)
The WdfUsbInterfaceGetNumConfiguredPipes method returns the number of pipes that are configured for a specified USB device interface.
wdf\wdfusbinterfacegetnumconfiguredpipes.htm
wdf
02/26/2018
WdfUsbInterfaceGetNumConfiguredPipes function
DFUsbRef_4273baba-c0e8-4bda-b6da-c9c9f00cabf9.xml, WdfUsbInterfaceGetNumConfiguredPipes, WdfUsbInterfaceGetNumConfiguredPipes method, kmdf.wdfusbinterfacegetnumconfiguredpipes, wdf.wdfusbinterfacegetnumconfiguredpipes, wdfusb/WdfUsbInterfaceGetNumConfiguredPipes
wdfusb.h
Wdfusb.h
Universal
1.0
2.0
DriverCreate, KmdfIrql, KmdfIrql2, UsbKmdfIrql, UsbKmdfIrql2
Wdf01000.sys (KMDF); WUDFx02000.dll (UMDF)
<=DISPATCH_LEVEL
Windows
WdfUsbInterfaceGetNumConfiguredPipes
wdfusb/WdfUsbInterfaceGetNumConfiguredPipes
APIRef
kbSyntax
LibDef
Wdf01000.sys
Wdf01000.sys.dll
WUDFx02000.dll
WUDFx02000.dll.dll
WdfUsbInterfaceGetNumConfiguredPipes

WdfUsbInterfaceGetNumConfiguredPipes function

-description

[Applies to KMDF and UMDF]

The WdfUsbInterfaceGetNumConfiguredPipes method returns the number of pipes that are configured for a specified USB device interface.

-parameters

-param UsbInterface [in]

A handle to a USB interface object that was obtained by calling WdfUsbTargetDeviceGetInterface.

-returns

WdfUsbInterfaceGetNumConfiguredPipes returns the number of pipes that are configured for the specified interface.

A bug check occurs if the driver supplies an invalid object handle.

-remarks

Your driver can call WdfUsbInterfaceGetNumConfiguredPipes after it has called WdfUsbTargetDeviceSelectConfig.

For more information about the WdfUsbInterfaceGetNumConfiguredPipes method and USB I/O targets, see USB I/O Targets.

Examples

The following code example obtains the number of pipes that are configured for a specified USB interface.

BYTE pipeCount;

pipeCount = WdfUsbInterfaceGetNumConfiguredPipes(UsbInterface);

-see-also

WdfUsbTargetDeviceGetInterface

WdfUsbTargetDeviceSelectConfig