summaryrefslogtreecommitdiffstats
path: root/commands
diff options
context:
space:
mode:
authorGiorgio Dal Molin <giorgio.nicole@arcor.de>2020-04-07 17:31:11 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2020-04-14 12:03:24 +0200
commitb1d30239ccde137bcd998437ef96d4af3a696415 (patch)
tree62fd0b0f35916e8f8724634b458ebc2075e86922 /commands
parent41594beb02d714e2641c70d36a442b1c1e1964e3 (diff)
downloadbarebox-b1d30239ccde137bcd998437ef96d4af3a696415.tar.gz
barebox-b1d30239ccde137bcd998437ef96d4af3a696415.tar.xz
ARM: i.MX: fixed enabling the MMU after switching in non secure mode.
The Domain Access Control Register (DACR) in CP15 is banked between secure and non secure mode: there a copy of the reg. in secure mode and a second copy in non secure mode. As barebox boots on the imx7 SOC it runs in secure mode and initializes the secure-mode copy of DACR (with 0x00000001). After switching to non secure mode, for example with the command 'smc -n' or while booting a kernel image with global.bootm.secure_state=nonsecure, the active value of DACR is the copy in non-secure mode and that copy was still uninitialized and in an UNKNOWN state. This caused the cpu to hang as soon as the MMU was enabled in non-secure mode. We fix this by reading the DACR value in secure mode just before switching to non secure and then initializing it again with the same value. Signed-off-by: Giorgio Dal Molin <giorgio.nicole@arcor.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'commands')
0 files changed, 0 insertions, 0 deletions