USBC_START_DEVICE_CALLBACK - NtDoc

Native API online documentation, based on the System Informer (formerly Process Hacker) phnt headers 
// usbbusif.h

USBC_START_DEVICE_CALLBACK UsbcStartDeviceCallback;

NTSTATUS UsbcStartDeviceCallback(
  [in]  PUSB_DEVICE_DESCRIPTOR DeviceDescriptor,
  [in]  PUSB_CONFIGURATION_DESCRIPTOR ConfigurationDescriptor,
  [out] PUSBC_FUNCTION_DESCRIPTOR *FunctionDescriptorBuffer,
  [out] PULONG FunctionDescriptorBufferLength,
  [in]  PDEVICE_OBJECT FdoDeviceObject,
  [in]  PDEVICE_OBJECT PdoDeviceObject
)
{...}
View the official Windows Driver Kit DDI reference

NtDoc

No description available.

Edit description on GitHub

Windows Driver Kit DDI reference (nc-usbbusif-usbc_start_device_callback)

USBC_START_DEVICE_CALLBACK callback function

Description

The USBC_START_DEVICE_CALLBACK routine allows a USB client driver to provide a custom definition of the interface collections on a device.

Parameters

DeviceDescriptor [in]

The device descriptor of the device.

ConfigurationDescriptor [in]

The configuration of the device.

FunctionDescriptorBuffer [out]

Pointer to a buffer that contains an array of function descriptors (USBC_FUNCTION_DESCRIPTOR).

FunctionDescriptorBufferLength [out]

The length in bytes of the buffer that FunctionDescriptorBuffer points to.

FdoDeviceObject [in]

The function device object for the device.

PdoDeviceObject [in]

The physical device object for the device.

Return value

If the operation succeeds, the vendor-supplied callback routine must return STATUS_SUCCESS.

Remarks

For a general description of the callback routine mechanism, see Customizing Enumeration of Interface Collections for Composite Devices.

See also

USBC_DEVICE_CONFIGURATION_INTERFACE_V1

View the official Windows Driver Kit DDI reference

Edit description on GitHub