On Thu, Oct 10, 2002 at 08:53:13AM -0700, David Brownell wrote: > > >>>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?
No, the bus handles disconnecting the different devices, and calling put_device() on the device itself (actually I think the name just got changed to unregister_device()) As USB knows that all children devices need to go away when the parent is disappearing, that logic has to stay within the USB core. thanks, greg k-h ------------------------------------------------------- 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
