>>>4. May I split usb_disconnect() into an interface and a usb_device part ? >> >>That needs other work too ... like, shouldn't the driver model core be >>handling children-first disconnect, which includes both interface >>shutdown and (for hubs) port shutdown? > > > We do child-first disconnect today. Are you not seeing this happen?
I'm seeing it (I think, though diagnostic/trace messages don't make that particularly apparent), but it's not coming from the driver model core as I'd expect. Since such sequencing was one of the original goals that was advertised for that work, shouldn't we be moving such logic out of USB? I could believe this is one of those areas that still needs work, even in the driver model code. But it's separate from the need for a "get rid of all current interfaces" facility internal to usbcore. - Dave ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
