Hi, On Wed, May 08, 2013 at 06:14:43PM +0200, Ben Dooks wrote: > >>>* Ben Dooks | 2013-05-07 22:06:33 [+0200]: > >>> > >>>>We are using an OMAP5432 ES2.0 on an UEVM board > >>>>and running into issues with the dwc3 usb. > >>> > >>>Sorry, I can't help at all. I don't have the board and I never had one. > >>>I had ES1.0 but I never got dwc3 to work. > >> > >>I have better news, re-based to 3.8.11 and it has now enumerated > >>the USB3 card reader at SuperSpeed. > >> > >>It seems the board is very picky about what it will play host to > >>as neither of the mini-b to A adapters I have work. I am using > >>a mini B to mini B cable to run the card reader. > >> > >>I have still got the disable CMD_RESET patch in. > > > >yeah, there are a few issues regarding CMD_RESET bit on the XHCI side > >with that IP. We're still trying to find a proper workaround. > > Is replacing the xhci-hcd.c reset command with a call to the dwc3 > driver not enough? I will leave this for the moment if it is being > worked on. > > Even if we are just working in gadget mode, having the xhci-hcd driver > around causes the system to stop working.
yeah, basically CMD_RESET (which is set during XHCI probe) causes some Global and Device Endpoint registers to corrupt. no workaround yet, other than constantly resetting the whole thing when you want to switch roles. What you can do, however, is to choose in Kconfig to have it working as peripheral only, then you're safe. -- balbi
signature.asc
Description: Digital signature
