> > Hi, > > > > On Tue, Aug 13, 2013 at 08:04:26PM +0000, Paul Zimmerman wrote: > > > > From: Felipe Balbi > > > > Sent: Tuesday, August 13, 2013 12:20 PM > > > > > > > > On Mon, Aug 05, 2013 at 03:41:57PM +0000, Wang, Yu Y wrote: > > > > > Hi Balbi, > > > > > > > > > > Please check the attached logs. The kernel base one kernel3.10. > > > > > > > > you didn't take the regdump after xHCI :-( I need to check if > > > > erst_base is being mirrored to DEPCMDPAR* > > > > > > Hi Felipe, > > > > > > There seems to be some basic misunderstanding here. ALL versions of > > > the Synopsys core share the internal RAM between device and host > > > modes. So the only supported way of switching modes is to shut down > > > the driver for the mode you are leaving, then start up the driver > > > for the mode you are entering and re-initialize (most of) the registers. > > > > > > This is described in the databook in the OTG -> Software Flow and > > > OTG > > > -> Programming Model chapters. > > > > sure. > > > > > So whether a particular set of RAM-based registers is mirrored > > > between modes does not matter. > > > > fair enough. > > > > > And I don't see what this has to do with hibernation? [Yu:] Sorry. Miss this question. For hibernation mode, if not met disconnect case, then needn't do soft-reset. But for disconnect case, spec said need to re-initialization. Because when controller enter hibernation mode, all backup data will be store in the hiber-storage inside of U2PMU/U3PMU. But for disconnect case, the spec said need to do "Device Power-On or Soft Reset"(2.50a spec 12.2.3.5). The reset will reset the PMU along with vaux_reset. Then all backup data will be lost. So driver have to re-initialization all registers. > > > > I have lost track of the conversation, probably. but I believe Yu > > mentioned resetting the IP everytime when coming out of hibernation > > and, for whatever reason, I confused myself with the other problem. > > > > [Yu:] Correct. We have to re-initialization device and host stack before switch to > corresponding mode. > > And we will planning to upstream some patches in the near future. > Include one common DWC3 OTG driver which maintain one OTG state machine, > support USB charger detection and role switch. And it need one hardware ops > structure registered by platform dependent driver to implemented. > > And also have separate drivers for host/otg/udc implementation for Intel > mobile platforms. > > If they can be merged. We will submit patches for hibernation feature base on > them. > > We are still preparing clear up our patches. OTG and host almost done. The > device mode patches still doing now. > > After all things done, I will send them to review. > > Thanks Balbi. > > > -- > > balbi -- 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
