On Mon, 13 Sep 2004, David Brownell wrote: > The IRQ handler can't do much at all; it just got an IRQ that > said the HC died. Resetting the controller is about all it can > do (so it's in a known and "safe" state), other than notifying > usbcore that it's cleanup-time. > > A more interesting question is whether usbcore should try > to actually restart the HCD. Eventually that'd be nice to > do, but for now the infrastructure seems lacking. So I'd > be content to just see all devices get cleanly shut down.
But what should happen to the root hub? It shouldn't be disconnected, because the HCD will try to deregister it later on. Should it be left in the CONFIGURED state or changed to the NOTATTACHED state? Should the hub driver be unbound? Or should the HCD's stop() routine be called, which will deallocate everything associated with the root hub? (That would make it easy to restart the HC later; just call the start() routine.) > Right now I'm > trying to find out what's up with resume after suspend-to-disk, > which is actually somewhat related (the root hub does get > reset), but other than pmcore problems I think the main issue > is root hub timers not getting restarted right. This gets into that whole tricky area of power-off resets we discussed in the spring. Are usb_devices supposed to be preserved across suspend-to-disk? Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: thawte's Crypto Challenge Vl Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam Camcorder. More prizes in the weekly Lunch Hour Challenge. Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
