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:udecxusbdevice.UdecxUsbDeviceInitSetEndpointsType

UdecxUsbDeviceInitSetEndpointsType function (udecxusbdevice.h)

Indicates the type of endpoint (simple or dynamic) in the initialization parameters that the client driver uses to create the virtual USB device.

buses\udecxusbdeviceinitsetendpointstype.htm

usbref

05/07/2018

UdecxUsbDeviceInitSetEndpointsType function

UdecxUsbDeviceInitSetEndpointsType, UdecxUsbDeviceInitSetEndpointsType function [Buses], buses.udecxusbdeviceinitsetendpointstype, udecxusbdevice/UdecxUsbDeviceInitSetEndpointsType

udecxusbdevice.h

Udecx.h

Windows

Windows 10

Windows Server 2016

1.15

Udecxstub.lib

PASSIVE_LEVEL

Windows

UdecxUsbDeviceInitSetEndpointsType

udecxusbdevice/UdecxUsbDeviceInitSetEndpointsType

APIRef

kbSyntax

LibDef

Udecxstub.lib

Udecxstub.dll

UdecxUsbDeviceInitSetEndpointsType

UdecxUsbDeviceInitSetEndpointsType function

-description

Indicates the type of endpoint (simple or dynamic) in the initialization parameters that the client driver uses to create the virtual USB device.

-parameters

-param UdecxUsbDeviceInit [in, out]

A pointer to a WDF-allocated structure that contains initialization parameters for the virtual USB device. The client driver retrieved this pointer in the previous call to UdecxUsbDeviceInitAllocate.

-param UdecxEndpointType [in]

A UDECX_ENDPOINT_TYPE-type value that indicates the type of USB endpoint.

-remarks

Before creating the virtual USB device, the client driver must indicate the type of endpoint it supports. It can support one of two types (defined in UDECX_ENDPOINT_TYPE):

Simple endpoint-The client driver creates all endpoint objects before plugging in the device. The device must have only one configuration and one interface setting per interface.
Dynamic endpoint-The client creates endpoint objects in the EVT_UDECX_USB_DEVICE_ENDPOINTS_CONFIGURE callback function. The USB device emulation class extension (UdeCx) invokes the driver's implementation when it gets a request to add or configure endpoints.

The UdecxUsbDeviceInit is an opaque structure that contains pointers to callback functions related to endpoints. If the client driver supports dynamic endpoints, then these callback functions must be implemented by the driver: