All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Mloduchowski <tomasz.mloduchowski@xlogic.pl>
To: balbi@ti.com
Cc: linux-omap@vger.kernel.org
Subject: Re: twl4030_usb porting advice
Date: Fri, 17 Dec 2010 07:23:43 +0000	[thread overview]
Message-ID: <4D0B0FFF.6020409@xlogic.pl> (raw)
In-Reply-To: <20101216090956.GG2601@legolas.emea.dhcp.ti.com>

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


  reply	other threads:[~2010-12-17  7:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15 11:55 twl4030_usb porting advice Tomasz Mloduchowski
2010-12-15 12:10 ` Felipe Balbi
2010-12-15 12:27   ` Tomasz Mloduchowski
2010-12-15 12:39     ` Felipe Balbi
2010-12-15 13:09       ` Tomasz Mloduchowski
2010-12-16  9:09         ` Felipe Balbi
2010-12-17  7:23           ` Tomasz Mloduchowski [this message]
2010-12-17 10:11             ` Felipe Balbi
2010-12-17 11:14               ` Tomasz Mloduchowski
2010-12-17 12:43                 ` Felipe Balbi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D0B0FFF.6020409@xlogic.pl \
    --to=tomasz.mloduchowski@xlogic.pl \
    --cc=balbi@ti.com \
    --cc=linux-omap@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.