linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: andy@warmcat.com (Andy Green)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] fix occasional ULPI timeouts with ehci-mxc
Date: Wed, 02 Dec 2009 19:35:33 +0000	[thread overview]
Message-ID: <4B16C185.80905@warmcat.com> (raw)
In-Reply-To: <37367b3a0912021058j2801df5l2c937ac339bc5f6b@mail.gmail.com>

On 12/02/09 18:58, Somebody in the thread at some point said:

Hi -

> mx27# usb 2-1: new low speed USB device using mxc-ehci and address 2
> hub 2-0:1.0: unable to enumerate USB device on port 1
>
> What you think about it?

What did you do with your chip select line on the ULPI PHY?

The first iMX LiteKIT board I had was an old revision where they had 
tied the PHY chip select pin asserted.  The ULPI PHY acted braindamaged 
because glitchy junk from during poweron / reset was taken as real data 
and it never recovered during the session.

Later versions of the LiteKIT changed this to be pulled deasserted and a 
GPIO can drive it asserted after reset is all done.  After I got a later 
revision with that mod, and drove the GPIO, suddenly all was well.

Never going to get that week back though.

-Andy

  reply	other threads:[~2009-12-02 19:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 16:13 [PATCH 1/1] fix occasional ULPI timeouts with ehci-mxc Valentin Longchamp
2009-12-02 16:49 ` Daniel Mack
2009-12-02 17:05   ` Valentin Longchamp
2009-12-03 10:35     ` Valentin Longchamp
2009-12-03 10:55       ` Daniel Mack
2009-12-02 17:36   ` Eric Bénard
2009-12-02 18:58 ` Alan Carvalho de Assis
2009-12-02 19:35   ` Andy Green [this message]
2009-12-02 20:25     ` Alan Carvalho de Assis
2009-12-02 21:13       ` Andy Green
2009-12-03  8:03         ` Valentin Longchamp
2009-12-03 14:45         ` Alan Carvalho de Assis
2009-12-03 14:53           ` Andy Green
2009-12-03 16:21             ` Alan Carvalho de Assis
2009-12-03 16:29               ` Daniel Mack
2009-12-03 16:37                 ` Alan Carvalho de Assis
2009-12-03 19:36               ` Robert Schwebel
2009-12-04  7:45                 ` javier Martin

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=4B16C185.80905@warmcat.com \
    --to=andy@warmcat.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).