16 Jan
2015
16 Jan
'15
12:49 a.m.
On 01/13/2015 12:45 PM, Ian Campbell wrote:
In this case the secure code lives in RAM, and hence needs to be reserved, but it has been relocated, so the reservation of __secure_start does not apply.
Add support for setting CONFIG_ARMV7_SECURE_RESERVE_SIZE to reserve such a region.
This will be used in a subsequent patch for Jetson-TK1
It's rather hard to review this without any documentation in the README, of the new symbol, or any of the existing:
CONFIG_ARMV7_NONSEC CONFIG_ARMV7_VIRT CONFIG_ARMV7_PSCI
It'd be nice to have a description of what those do exactly, and how they interact or conflict.