| commit | baf6b6815ba9ae8255eefd1ddf15216d53da34b5 | |
| author | Peter Crosthwaite <crosthwaitepeter@gmail.com> | |
| Tue, 10 Nov 2015 13:37:33 +0000 (10 13:37 +0000) | ||
| committer | Peter Maydell <peter.maydell@linaro.org> | |
| Tue, 10 Nov 2015 13:37:33 +0000 (10 13:37 +0000) | ||
| tree | 712795f8fc9759c3cc4bd3de7aa4b05d8fd592af | treesnapshot (tar.gz zip) |
| parent | b95690c9beaffd95edf91eb67829dc1e0a81e666 | commitdiff |
arm: boot: Add secure_board_setup flag
Add a flag that when set, will cause the primary CPU to start in secure
mode, even if the overall boot is non-secure. This is useful for when
there is a board-setup blob that needs to run from secure mode, but
device and secondary CPU init should still be done as-normal for a non-
secure boot.
Signed-off-by: Peter Crosthwaite <crosthwaite.peter@gmail.com>
Message-id: d1170774d5446d715fced7739edfc61a5be931f9.1447007690.git.crosthwaite.peter@gmail.com
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Add a flag that when set, will cause the primary CPU to start in secure
mode, even if the overall boot is non-secure. This is useful for when
there is a board-setup blob that needs to run from secure mode, but
device and secondary CPU init should still be done as-normal for a non-
secure boot.
Signed-off-by: Peter Crosthwaite <crosthwaite.peter@gmail.com>
Message-id: d1170774d5446d715fced7739edfc61a5be931f9.1447007690.git.crosthwaite.peter@gmail.com
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
| hw/arm/boot.c | diffblobblamehistory | |
| include/hw/arm/arm.h | diffblobblamehistory |