ARM: OMAP2+: hwmod/timer: first set of cleanups for 3.4
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 7 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 7 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/7] ARM: OMAP2+: hwmod/timer: first set of cleanups for 3.4
Quoted 10 lines · Paul Walmsley
Hi
Quoted 6 lines · Benoit
Thanks to the L3 log error:
[ 0.838439] L3 custom error: MASTER:DucatiM3 TARGET:GPMCI guess that I understand why I was not releasing the hardreset at boot time before:-)
Quoted 8 lines
Quoted 6 lines
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().
Ooops, you're right we were talking about asserting the reset not de-asserting it.
Quoted 5 lines
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.
So maybe in that case, this is because the reset line is already de-asserted by the fast boot and by enabling the clock we start executing some random code in the CortexM3... but this is still weird that this error was not happening before.
Regards,
Benoit