[U-Boot] [Question][i.MX6q] Is it possible to configure and use the USB-OTG as EHCI host only?
Hi All,
I am Rafal and this is my first post here, so I would like to say hello to everyone :)
I have been using the Sabrelite board (i.MX6Q) from Boundary Devices for some time and now I have been working on U-Boot. The code I use is based on the mainline U-Boot.
The current implementation supports USB Host1 only, but I would like to use OTG configured as host (I do not need support for device mode). I wanted to implemet the lowest layer for the EHCI driver like it is done for Host1 (in fact the offset of the USB controller's registers set is different and few things like GPIOs) but it does not seem to work. The result is that the U-Boot creates the EHCI hub, but no device is detected on Port 1. I am expecting something like "Port 1 Status 503 Change 1" but I get "Port 1 Status 502 Change 0".
I suppose it is possible to use USG-OTG instead of Host1 as EHCI host in U-Boot somehow. Is there something I am missing?
By the way, the device is connected via special adapter and the power (5V) is provided to it.
Kind regards, Rafal
Hi,
On Tue, Mar 12, 2013 at 1:04 PM, Rafał Fabich rafal.fabich@gmail.com wrote:
I suppose it is possible to use USG-OTG instead of Host1 as EHCI host in U-Boot somehow. Is there something I am missing?
Sorry for answering to myself, but the problem is solved. In fact the controller had to be reinitialized after EHCI reset.
Regards, Rafal
Hi Rafal,
On Wed, Mar 13, 2013 at 12:34 PM, Rafał Fabich rafal.fabich@gmail.com wrote:
Hi,
On Tue, Mar 12, 2013 at 1:04 PM, Rafał Fabich rafal.fabich@gmail.com wrote:
I suppose it is possible to use USG-OTG instead of Host1 as EHCI host in U-Boot somehow. Is there something I am missing?
Sorry for answering to myself, but the problem is solved. In fact the controller had to be reinitialized after EHCI reset.
Care to submit a patch for this?
On 03/13/2013 08:34 AM, Rafał Fabich wrote:
Hi,
On Tue, Mar 12, 2013 at 1:04 PM, Rafał Fabich rafal.fabich@gmail.com wrote:
I suppose it is possible to use USG-OTG instead of Host1 as EHCI host in U-Boot somehow. Is there something I am missing?
Sorry for answering to myself, but the problem is solved. In fact the controller had to be reinitialized after EHCI reset.
Regards, Rafal
Got patch?
Hi,
On Wed, Mar 13, 2013 at 5:33 PM, Eric Nelson eric.nelson@boundarydevices.com wrote
Got patch?
On Wed, Mar 13, 2013 at 5:32 PM, Fabio Estevam festevam@gmail.com wrote:
Care to submit a patch for this?
Yes, I would like to do that, but first I have to do some more testing (ie. the ext2 partition, etc). Anyway, before I submit the patch, I would like to ask one question: My current implementation does not support the OTG in Device mode. It only provides the OTG controller instead of Host1 as the lowest layer for the EHCI driver. So, basically it is a fixed host-only solution that uses the OTG port. Is it enough for the patch? :)
Best regards, Rafal
On Wed, Mar 13, 2013 at 6:13 PM, Rafał Fabich rafal.fabich@gmail.com wrote:
Hi,
On Wed, Mar 13, 2013 at 5:33 PM, Eric Nelson eric.nelson@boundarydevices.com wrote
Got patch?
On Wed, Mar 13, 2013 at 5:32 PM, Fabio Estevam festevam@gmail.com wrote:
Care to submit a patch for this?
Yes, I would like to do that, but first I have to do some more testing (ie. the ext2 partition, etc). Anyway, before I submit the patch, I would like to ask one question: My current implementation does not support the OTG in Device mode. It only provides the OTG controller instead of Host1 as the lowest layer for the EHCI driver. So, basically it is a fixed host-only solution that uses the OTG port. Is it enough for the patch? :)
Should be fine, you can explain it in the commit log.
We do not have udc support for i,mx in U-boot yet, so working in host mode is all we can do at the moment.
Thanks,
Fabio Estevam
participants (3)
-
Eric Nelson -
Fabio Estevam -
Rafał Fabich