From: Kevin Hilman <khilman@mvista.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: MUSB: unreliable OTG detection in host mode
Date: Fri, 31 Aug 2007 17:29:03 -0700 [thread overview]
Message-ID: <46D8B24F.3010409@mvista.com> (raw)
In-Reply-To: <20070901002025.B8E79235120@adsl-69-226-248-13.dsl.pltn13.pacbell.net>
David Brownell wrote:
>> On 2430, I've noticed that using the driver built in OTG mode, the
>> detection of devices in host-mode is unreliable.
>
> Unreliable in what way(s)?
Meaning it sometimes detects connected devices and sometimes not.
Sometimes a reboot and another try helps. But with recent git it seems
to never detect devices.
>
>> Building the driver in
>> only host mode doesn't have any problems with the same devices connected.
>>
>> I load the musb_hdrc module, then the g_zero module to initiate OTG
>> detection.
>>
>> If my board is connected as a gadget, this works just fine, but if my
>> board is the host and I have devices connected, the detection doesn't
>> work reliably. In the past it seemed it would work most of the time,
>> but with the latest kernel, it doesn't seem to work at all.
>
> This somewhat resembles a problem I've not tracked down, whereby
> the 2420 + TUSB6010-EVM, in OTG mode, seems to recieve garbage
> when reading descriptors from the high speed hub I usually like
> to connect as a root device.
>
> DaVinci didn't seem to have any such issues...
>
I haven't tested DaVinci in OTG mode since on the EVM board I have, you
have to move a jumper to switch between the two.
Kevin
next prev parent reply other threads:[~2007-09-01 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-01 0:05 MUSB: unreliable OTG detection in host mode Kevin Hilman
2007-09-01 0:20 ` David Brownell
2007-09-01 0:29 ` Kevin Hilman [this message]
2007-09-01 2:14 ` David Brownell
2007-09-01 4:55 ` Kevin Hilman
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=46D8B24F.3010409@mvista.com \
--to=khilman@mvista.com \
--cc=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox