Thread (5 messages) 5 messages, 3 authors, 2012-01-31
STALE5240d

[PATCH 0/7] ARM: OMAP2+: hwmod/timer: first set of cleanups for 3.4

From: paul@pwsan.com (Paul Walmsley)
Date: 2012-01-31 08:14:53
Also in: linux-omap

Possibly related (same subject, not in this thread)

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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help