USB Composite device driver loading and PnP events

NTDEV
1

I have a question on the USB composite device. In DDK, it is said After the USB hub driver generates a PnP event for a Composite device with a set of compatible IDs that include USB\COMPOSITE, Windows searches the INF files in the inf subdirectory of the Windows installation (and, possibly, a vendor-provided floppy disk) for a match. If the device ID is matched, Windows loads the single driver that is indicated by the installation script and the generic parent driver does not come into play. If no device ID match is found, Windows uses a compatible ID, for which it loads the USB generic parent driver.

I just want to know If the device ID is matched, Windows loads the single driver that is indicated by the installation scripts, then who will be responsible to generates PnP events for the multiple interfaces in the composite device?

2

> I just want to know If the device ID is matched, Windows loads the single
driver

that is indicated by the installation scripts, then who will be responsible to
generates PnP events for the multiple interfaces in the composite device?

Your driver will be responsible for this. You fully replace the MS’s generic
parent driver.

–
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

3

Typically if a vendor overrides the match on a composite device with their own driver, they will consume all of the interfaces on the device. For instance, take a Bluetooth radio which has 2 interfaces and does not let the composite driver load. It will consume both interfaces and expose them as one function, not 2 separate functions

d