On 12/16/10 09:09, Felipe Balbi wrote:
On Wed, Dec 15, 2010 at 01:09:42PM +0000, Tomasz Mloduchowski wrote:
On 12/15/10 12:39, Felipe Balbi wrote:
On Wed, Dec 15, 2010 at 12:27:10PM +0000, Tomasz Mloduchowski wrote:
I would gladly welcome any pointers that could help me solve this
issue.
you're connecting a FS/LS device to EHCI port, that doesn't work. OMAP
can't handle port handoff to companion OHCI controller, then it fails
not being able to enumerate the device. Try remuxing your port to OHCI
controller and disabling EHCI from Kconfig.
It actually is a HS device (it's a 4-port hub) - when booting the
vendor supplied kernel (based off 2.6.32, i.e. pre -IR redesign), the
device identifies as follows:
I've also made a mistake describing the pastebins - the working, PSP
kernel boot log is here:
http://pastie.org/1379102
while the non-working git kernel messages are here (with
CONFIG_USB_DEBUG):
http://pastie.org/1379100
I'm quoting a snippet below for commenting.
[ 1.639892] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.646759] ehci_hcd: block sizes: qh 60 qtd 96 itd 160 sitd 96
[ 1.646881] ehci-omap ehci-omap.0: failed to get ehci port1 regulator
This is alarming. Please add this patch to get the error code:
>
This is also alarming... Let's increase the timeout just for a debugging
purpose:
I've applied both patches. The new kernel log in its entirety resides here:
http://pastie.org/1384896
And the line of interest is
[ 2.085449] ehci-omap ehci-omap.0: failed to get ehci port1 regulator
--> 0
Unfortunately, I don't understand what an error code of '0' might mean
here, but it surely does something.
Cheers,
Tomasz
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
