From: eric@eukrea.com (Eric Bénard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] fix occasional ULPI timeouts with ehci-mxc
Date: Wed, 02 Dec 2009 18:36:31 +0100 [thread overview]
Message-ID: <4B16A59F.7080004@eukrea.com> (raw)
In-Reply-To: <20091202164930.GG14091@buzzloop.caiaq.de>
Daniel Mack a ?crit :
> On Wed, Dec 02, 2009 at 05:13:01PM +0100, Valentin Longchamp wrote:
>> On various mxc boards, the intial ULPI reads resulted in a timeout
>> which prevented the transceiver to be identified and thus the ehci
>> device to be probed.
>>
>> Initializing the hardware lines connected to the transceiver (through
>> pdata->init call) before actually enabling clocks and configuring
>> registers in the devices fixes this problem.
>
> Hmm, glad to hear it fixed your problem :) However, there is no real
> ULPI communication done on the viewports before the board specific
> init function is called, and the timeouts that are reported come from
> the transceiver probing which is called at a later point.
>
> Even with that patch applied, one board I have here fails to initialize
> the OTG port.
>
can you probe the DIR signal (pin 19) of the ISP1504 when you have the
problem ?
Eric
next prev parent reply other threads:[~2009-12-02 17:36 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 [this message]
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
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=4B16A59F.7080004@eukrea.com \
--to=eric@eukrea.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).