> The USB subsystem only binds drivers to USB "interfaces". A USB device
> may have many "interfaces", so a single device may have many drivers
> attached to it, handling different portions of it (think of a USB
> speaker, which has a audio driver for the audio stream, and a HID driver
> for the speaker buttons.) Because of this I had to create a "empty"
> device driver that I attach to the USB device structure. This ensures
> it shows up properly in the driverfs tree, and that no USB drivers try
> to bind to it.
the probe/disconnect changes are an improvement.
But what do we call a device? IMHO the device in
terms of driverfs is the interface, thus the usb_device
should be seen as a bus, which interfaces are attached to.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/