Hi Georg,
> > > IMHO this should be the job of usbcore, as the HCD has (except for its root
> > > hub) no knowledge of the connected devices and their status. Then each HCD
> > > only needs to handle the HW stuff for suspend/resume.
> >
> > Right. Though the lines between the hub driver (part of usbcore)
> > and the "upper part" of any given HCD get pretty fuzzy. Plus, there
> > is currently no primitive through which any part of "usbcore" can
> > ask the HCD to do that suspend/resume.
>
> That seems easy. What about an additional entry in the usb_operations
> structure?
Maybe. But I think the "usb_bus" layer deserves a more serious
rewhack than that. It just doesn't support sharing enough behavior
between the various HCDs. I'd rather see that rework done in a
more comprehensive manner than that. For the existing HCDs,
that sounds like a 2.5 issue.
- Dave
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
