Hi,
going through the drivers, it seems that there are drivers which legitimately use usb_set_configuration. It seems that we have to deal with it.
Some drivers, cdc-acm, -ether, really take the whole device and try all configurations.
We should remove cdc-ether.c now, 2.5 doesn't need it.
As for cdc-acm, I don't think it should be doing that. The code that chooses a configuration can reasonably change its mind, for example if there was a choice and no driver could bind to that initial selection ... I don't think probe() should be allowed to change configurations.
Some like empeg and other serial drivers use it where altsettings should be used. Other like tiglusb use it as a "soft reset".
That is, they're all using it to reset device state, including endpoints?
Changing configuration from current, to zero, back to current, might be a reasonable thing to package as a generic soft reset capability. One that doesn't affect driver binding, but also doesn't involve any "re-enumerate from POWERED state" logic.
- Dave
What is to be done?
Regards Oliver
------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
