> From: Kevin Hilman [mailto:khilman@xxxxxxxxxxxxxxxxxxx] > Sent: Thursday, June 18, 2009 10:03 AM > > I've seen this issue on a couple custom boards. In these instances > > I've not had access to boot loaders. I would expect this issue > > would show up in the wild in some devices. It might be ok to move > > to at least init. Having it at deadlock spot is a bit more > > conservative. > > Richard, since Paul and I cannot reproduce this currently, would you be able > to test > if a fix at init fixes the problems that you've seen? I did up the fix at this spot for a couple reasons. -1- This is where it was locked up... -2- This kind of operation needs to happen in uncached sram Doesn't doing at 1st init require pushing of another sram? Also as its not conclusive what causes it to enter this state other than SDRC_POWER association its safer to do it here. I think the boot loader should have tried to do this correctly. But I really don't know what it did. Regards, Richard W. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
