Hi On Tue, 31 Jan 2012, Cousson, Benoit wrote: > Thanks to the L3 log error: > [ 0.838439] L3 custom error: MASTER:DucatiM3 TARGET:GPMC > > I guess that I understand why I was not releasing the hardreset at boot time > before:-) > > DSP and CortexM3 cannot be released from reset until someone loaded a firmware > in memory. Otherwise they will start executing some random instructions that > in this case are trying to access an area that is not accessible. > > We have to let the driver handle the hardreset because it is mainly used for > processors. Currently we're not asserting hardreset in the hwmod code during _reset(). I had that patch in the series at some point, but took it out before posting it. So maybe that might resolve this particular issue. Also sounds like we should make sure that we keep the processor IPs in hardreset until some driver explicitly releases it; we'll need to make sure the code does that too. - Paul -- 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
