From: Felipe Balbi <me@felipebalbi.com>
To: David Brownell <david-b@pacbell.net>
Cc: me@felipebalbi.com, Jeff Steele <jsteele@coloradocollege.edu>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: status of USB on omap35xx ?
Date: Wed, 10 Dec 2008 21:01:01 +0200 [thread overview]
Message-ID: <20081210190100.GF9799@frodo> (raw)
In-Reply-To: <200812101028.25235.david-b@pacbell.net>
On Wed, Dec 10, 2008 at 10:28:25AM -0800, David Brownell wrote:
> I don't know the details, but the big problem with EHCI
> on OMAP3 is evidently some kind of silicon issue that
> shows up through the transceiver hookup and prevents the
> link from being reliable. I'm told that some boards using
> that without a transceiver -- for on-board communication,
> not for an external link -- have been successful.
>
> Folk at TI were looking at those issues; I don't know if
> they've been resolved yet, e.g. in the ES 3.0 silicon.
Oh yeah, that's right. There was some pin-incompatibility with ohci
which prevented port handoffs to be done reliably, or something like
that.
If I'm not wrong, once the port is handed over to ohci, it can never
switch back to ehci and it dies.
Can't really remember if this is the right issue since I haven't been
working too much with ehci :-p
--
balbi
next prev parent reply other threads:[~2008-12-10 19:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 0:50 status of USB on omap35xx ? Jeff Steele
2008-12-10 14:46 ` Felipe Balbi
2008-12-10 16:33 ` Jeff Steele
2008-12-10 17:40 ` Felipe Balbi
2008-12-10 18:28 ` David Brownell
2008-12-10 19:01 ` Felipe Balbi [this message]
2008-12-10 19:48 ` Pandita, Vikram
2008-12-10 23:02 ` Steve Sakoman
2008-12-11 0:57 ` Tony Lindgren
2008-12-11 10:38 ` Grazvydas Ignotas
2008-12-11 16:49 ` Paul Walmsley
2008-12-11 17:38 ` Steve Sakoman
2008-12-11 20:41 ` Grazvydas Ignotas
2008-12-11 21:07 ` Paul Walmsley
2008-12-11 22:52 ` Grazvydas Ignotas
2008-12-11 23:09 ` Paul Walmsley
2008-12-12 20:15 ` Grazvydas Ignotas
2008-12-12 20:33 ` Paul Walmsley
2008-12-12 21:01 ` Pandita, Vikram
2008-12-12 21:12 ` Paul Walmsley
2008-12-12 21:21 ` Pandita, Vikram
2008-12-21 22:25 ` Gadiyar, Anand
2008-12-22 12:21 ` Felipe Balbi
2008-12-12 20:35 ` Steve Sakoman
2008-12-12 22:54 ` Grazvydas Ignotas
2008-12-12 2:16 ` David Brownell
2008-12-11 21:54 ` Steve Sakoman
2008-12-11 22:32 ` David Brownell
2008-12-12 1:56 ` Tony Lindgren
2008-12-11 17:40 ` Steve Sakoman
2008-12-11 18:14 ` Paul Walmsley
2008-12-11 18:20 ` Pandita, Vikram
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=20081210190100.GF9799@frodo \
--to=me@felipebalbi.com \
--cc=david-b@pacbell.net \
--cc=jsteele@coloradocollege.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox