dwc3 on omap5432 no SuperSpeed host mode
We are using an OMAP5432 ES2.0 on an UEVM board and running into issues with the dwc3 usb. The first issue is that the xhci reset code stops the entire core from working after it is executed. We have commented the xhci reset code from issuing the CMD_RESET and this has allowed us to get the XHCI platform driver to work in some capacity (and swap back to gadget mode if needed). Is the xhci_reset issue known? Should I supply a patch to allow the platform code to override the xhci reset with a custom reset hook? The second issue is that once this is working, we have not been able to get the board to function as a SuperSpeed host (it will work as a SuperSpeed gadget to a Linux PC). Any device plugged in (we are testing with a pen-drive, a usb3 network adapter and a usb3 transcend card reader) will either fail to enumerate at-all, or if it does get detected it falls back to high-speed (which does work). I can supply logs if needed. -- Ben Dooks, Senior Engineer http://www.codethink.co.uk/ -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dwc3 on omap5432 no SuperSpeed host mode
* 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. Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dwc3 on omap5432 no SuperSpeed host mode
On 08/05/13 17:45, Sebastian Andrzej Siewior 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. -- Ben Dooks http://www.codethink.co.uk/ Senior Engineer Codethink - Providing Genius -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dwc3 on omap5432 no SuperSpeed host mode
Hi, On Wed, May 08, 2013 at 05:52:50PM +0200, Ben Dooks wrote: > On 08/05/13 17:45, Sebastian Andrzej Siewior 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. On your mini-b to A adapters, make sure ID pin is grounded, if it's not then the Vbus regulator won't switch to bypass mode, that's something workable in SW, however, just lack of time to implement. -- balbi signature.asc Description: Digital signature
Re: dwc3 on omap5432 no SuperSpeed host mode
On 08/05/13 18:02, Felipe Balbi wrote: Hi, On Wed, May 08, 2013 at 05:52:50PM +0200, Ben Dooks wrote: On 08/05/13 17:45, Sebastian Andrzej Siewior 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. On your mini-b to A adapters, make sure ID pin is grounded, if it's not then the Vbus regulator won't switch to bypass mode, that's something workable in SW, however, just lack of time to implement. I've forced the palmas-pmic to run Vbus all the time at the moment, as it didn't have any sort of controls for SMSP10 output 1. Thankyou for the response. -- Ben Dooks http://www.codethink.co.uk/ Senior Engineer Codethink - Providing Genius -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dwc3 on omap5432 no SuperSpeed host mode
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
Re: dwc3 on omap5432 no SuperSpeed host mode
On 15/05/13 15:09, Felipe Balbi wrote: 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. Ok, I was under the impression that it was needed even for host only. We still have not managed to get a stable xhci host mode on the OMAP5432-UEVM board at SuperSpeed. -- Ben Dooks http://www.codethink.co.uk/ Senior Engineer Codethink - Providing Genius -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dwc3 on omap5432 no SuperSpeed host mode
Hi, On Wed, May 15, 2013 at 03:15:44PM +0100, Ben Dooks wrote: > 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. > > Ok, I was under the impression that it was needed even for host only. > > We still have not managed to get a stable xhci host mode on the > OMAP5432-UEVM board at SuperSpeed. funny, we tested this a few days back. Right now I don't have HW with me (travelling), but Kishon has. Maybe he can help us out ? -- balbi signature.asc Description: Digital signature
Re: dwc3 on omap5432 no SuperSpeed host mode
On 15/05/13 15:30, Felipe Balbi wrote: Hi, On Wed, May 15, 2013 at 03:15:44PM +0100, Ben Dooks wrote: 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. Ok, I was under the impression that it was needed even for host only. We still have not managed to get a stable xhci host mode on the OMAP5432-UEVM board at SuperSpeed. funny, we tested this a few days back. Right now I don't have HW with me (travelling), but Kishon has. Maybe he can help us out ? It would be useful to find out which version of the kernel and u-boot where used. -- Ben Dooks http://www.codethink.co.uk/ Senior Engineer Codethink - Providing Genius -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
