On Fri, 14 Jun 2013, Chao Xie wrote: > I checked with the code in our 3.4 git. we really did a lot of things > when suspend/resume, and at that point the patch for ehci_resume and > ehci_suspend are not added. > i think the driver can make use of ehci_resume/ehci_suspend. > For PHY, we have to initialize it and shutdown it when do > suspend/resume. Our PHY do not have any suspend states. > I suppose these phy operation have to be handled by each ehci driver > owner only, or you think it can be handled at ehci-hce level?. If the operations are the same for each platform, then yes -- they could be done in ehci-hcd. But if different platforms handle their PHYs differently then each glue module will need to do this on its own. 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
