On Fri, 19 Oct 2012, Pavan Kondeti wrote: > Why are we having this check in ehci_suspend()? By the time > ehci_suspend() is called, ehci_bus_suspend() is already called in > which next_statechange is updated. we might end up giving 10msec delay > in ehci_suspend(). Yes. I don't know the reason for the check in ehci_suspend; I didn't write it originally. Probably we can get rid of the checks in ehci_suspend and ehci_resume. I don't know of any reason why a controller can't be switched back to full power immediately after going to low power. > why is 100 msec delay in ehci_resume? ehci_bus_resume has only 5 msec delay. It's probably a typo. > > Would you like to write a patch to do this? > > > > I will submit a patch next week. Okay, good. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
