[PATCH] omap4: Fix ULPI PHY init for ES1.0 SDP (Re: 4430SDP boot failure)

-----Original Message-----
From: linux-omap-owner at vger.kernel.org [mailto:linux-omap-
owner at vger.kernel.org] On Behalf Of Tony Lindgren
Sent: Thursday, February 24, 2011 11:09 PM
To: Santosh Shilimkar
Cc: Anand Gadiyar; Russell King - ARM Linux; linux-arm-
kernel at lists.infradead.org; linux-omap at vger.kernel.org; Keshava
Munegowda; Felipe Balbi
Subject: Re: [PATCH] omap4: Fix ULPI PHY init for ES1.0 SDP (Re:
4430SDP boot failure)

* Santosh Shilimkar [off-list ref] [110212 00:45]:

quoted

Tony,

quoted

-----Original Message-----
From: Santosh Shilimkar [mailto:santosh.shilimkar at ti.com]
Sent: Thursday, February 03, 2011 2:13 PM
To: Tony Lindgren
Cc: Anand Gadiyar; Russell King - ARM Linux; linux-arm-
kernel at lists.infradead.org; linux-omap at vger.kernel.org; Keshava
Munegowda; Felipe Balbi
Subject: RE: [PATCH] omap4: Fix ULPI PHY init for ES1.0 SDP (Re:
4430SDP boot failure)

quoted

-----Original Message-----
From: Tony Lindgren [mailto:tony at atomide.com]
Sent: Thursday, February 03, 2011 1:19 AM
To: Santosh Shilimkar
Cc: Anand Gadiyar; Russell King - ARM Linux; linux-arm-
kernel at lists.infradead.org; linux-omap at vger.kernel.org;

Keshava

quoted

quoted

quoted

Munegowda; Felipe Balbi
Subject: Re: [PATCH] omap4: Fix ULPI PHY init for ES1.0 SDP

(Re:

quoted

quoted

quoted

4430SDP boot failure)

* Santosh Shilimkar [off-list ref] [110201 22:04]:

quoted

quoted

It's a ES1.0 blaze, with the patch below it reboots early
during the boot. I also have to disable omap_l2_cache_init
on this board to get it to boot.

Do you still get this problem with 'omap_l2_cache_init' ?
As reported earlier, we don't see this issue on ES1.0
SDP.

Yeah I do, it rarely makes it to the userspace. Works reliably
if I disable omap_l2_cache_init.

Ok. I shall try few experiments and try to reproduce it

Not sure if it's the same issue but I managed to reproduce the
issue on ES2.0 itself. And after some experiments, it boiled
down to the V6 and V7 issue. By disabling OMAP2 from the build,
everything was fine again.

Was this with linux-omap master branch or mainline?

The V6 vs V7 issues should be sorted out with Russell's patches that
we also have now in linux-omap master branch.

This was with mainline.
Then I applied RMK's series and things were OK.