Hi Dave, I've been looking at ehci_shutdown() in ehci-hcd.c with increasing puzzlement.
Why shut off port power before attempting to stop the host controller from processing the periodic and async schedules? It seems like you want to allow the host to complete whatever transactions it was in the middle of. If ehci_shutdown() is trying to stop attach/detach notifications, that will only work if the host controller supports port power switching. ehci_shutdown() also calls ehci_reset() after shutting down the schedules. However, AFAIK the run/stop bit is never set before ehci_reset() is called. The EHCI specification says that resetting a running HC is "will result in undefined behavior." ehci_quiesce() is only called from ehci_shutdown(), so why not send a halt command there? Some of these answers may be in the bitkeeper history, but that's taking a while to download. :) Sarah Sharp - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
