All of lore.kernel.org
 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: Thu, 03 Dec 2009 14:53:56 +0000	[thread overview]
Message-ID: <4B17D104.4040800@warmcat.com> (raw)
In-Reply-To: <37367b3a0912030645m12db4f12j7991081e7d2bca00@mail.gmail.com>

On 12/03/09 14:45, Somebody in the thread at some point said:

Hi Alan -

> On 12/2/09, Andy Green<andy@warmcat.com>  wrote:
>> It's more a question about what that input on the PHY chip sees during
>> powerup / reset... it needs to be nicely and definitely high the whole
>> time so it will ignore what happens then.  Is it pulled up, or just
>> connected to the iMX GPIO?  iMX GPIO alone may not be enough.  They
>> mostly default to 100K pullup but even that may not be enabled early in
>> the powerup action.
>
> The CS_N pin is connected directly to GPIO (PA24) with no pull-up.
>
>> A 10K to your IO voltage rail on CS_N solved it for the LiteKIT and on
>> the boards we have made.
>
> I place a 10K resistor to pull-up and changed CS_N to low at usb
> platform init and it worked fine!
>
> Thank you very much!

You're super welcome... glad that time spent wandering in the desert was 
able to help someone else in the end :-)

-Andy

  reply	other threads:[~2009-12-03 14:53 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
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 [this message]
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=4B17D104.4040800@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 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.