USB confusion
What are the options to have USB Host support on the "normal" USB channels (i.e. not the OTG port)?
This used to work on my platform but things stopped when I upgraded to the latest kernel :-(
n.b. OTG host and gadget still work fine.
Thanks
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 10 lines · Gary Thomas
What are the options to have USB Host support on the "normal" USB channels (i.e. not the OTG port)?
This used to work on my platform but things stopped when I upgraded to the latest kernel :-(
n.b. OTG host and gadget still work fine.
Thanks
Following up on this, I made sure that CONFIG_USB_EHCI_HCD was defined.
Now I see these messages:
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Clock usbhost_48m_fck didn't enable in 100000 tries
ehci-omap: probe of ehci-omap.0 failed with error -22
Any ideas what else I might be missing?
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 8 lines · ext Gary Thomas
Following up on this, I made sure that
CONFIG_USB_EHCI_HCDwas defined.Now I see these messages:
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Clockusbhost_48m_fckdidn't enable in 100000 tries
ehci-omap: probe of ehci-omap.0 failed with error -22Any ideas what else I might be missing?
check what happens with that clock. Why is that timing out ?
I believe that message comes from clk fw. Maybe Paul could give us some hint. Paul ?
Signature · 1 line
balbi
Quoted 5 lines · Gary Thomas
What are the options to have USB Host support on the "normal" USB channels (i.e. not the OTG port)?
This used to work on my platform but things stopped when I upgraded to the latest kernel :-(
I had the same experience with Overo and posted a patch a couple of weeks ago to get it working (ARM: OMAP3: Overo: Fix EHCI initialization)
Beagle EHCI is also broken on top of tree and requires a couple of changes in the board file. I'll try to submit that patch in the next day or so.
Steve
Quoted 10 lines · Steve Sakoman
Quoted 5 lines · Gary Thomas
What are the options to have USB Host support on the "normal" USB channels (i.e. not the OTG port)?
This used to work on my platform but things stopped when I upgraded to the latest kernel :-(
I had the same experience with Overo and posted a patch a couple of weeks ago to get it working (ARM: OMAP3: Overo: Fix EHCI initialization)
That fixed it (more precisely, the indirectly referenced patch 'fix phy_reset' fixed my problem)
Thanks
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 16 lines
-----Original Message-----
From: [email protected] [mailto:linux-omap- [email protected]] On Behalf Of Felipe Balbi
Sent: Tuesday, September 01, 2009 9:58 PM
To: ext Gary Thomas
Cc: [email protected]; Paul Walmsley
Subject: Re: USB confusionQuoted 7 lines · ext Gary Thomas
Following up on this, I made sure that
CONFIG_USB_EHCI_HCDwas defined.Now I see these messages:
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Clockusbhost_48m_fckdidn't enable in 100000 tries
ehci-omap: probe of ehci-omap.0 failed with error -22
Quoted 6 lines
Quoted 1 line
Any ideas what else I might be missing?
check what happens with that clock. Why is that timing out ?
I believe that message comes from clk fw. Maybe Paul could give us some hint. Paul ?
I faced similar issue and it got solved with increased timeout value. Patch is already submitted for this:
[PATCH 5/9] ehci: increase timeout to fix ehci failure
http://marc.info/?l=linux-omap&m=124956053919660&w=2
-Ajay
Quoted 7 lines
--
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html