Searched hist:d6b72da029ab85b344b98b28b12d7cbe800b6cc4 (Results 1 – 3 of 3) sorted by relevance
| /rk3399_rockchip-uboot/arch/arm/cpu/armv7/ |
| H A D | virt-dt.c | d6b72da029ab85b344b98b28b12d7cbe800b6cc4 Tue Apr 21 05:18:32 UTC 2015 Jan Kiszka <jan.kiszka@siemens.com> virt-dt: Allow reservation of secure region when in a RAM carveout
In this case the secure code lives in RAM, and hence the memory node in
the device tree needs to be adjusted. This avoids that the OS will map
and possibly access the reservation.
Add support for setting CONFIG_ARMV7_SECURE_RESERVE_SIZE to carve out
such a region. We only support cutting off memory from the beginning or
the end of a RAM bank as we do not want to increase their number (which
would happen if punching a hole) for simplicity reasons
This will be used in a subsequent patch for Jetson-TK1.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Tom Warren <twarren@nvidia.com>
|
| /rk3399_rockchip-uboot/arch/arm/lib/ |
| H A D | bootm-fdt.c | d6b72da029ab85b344b98b28b12d7cbe800b6cc4 Tue Apr 21 05:18:32 UTC 2015 Jan Kiszka <jan.kiszka@siemens.com> virt-dt: Allow reservation of secure region when in a RAM carveout
In this case the secure code lives in RAM, and hence the memory node in
the device tree needs to be adjusted. This avoids that the OS will map
and possibly access the reservation.
Add support for setting CONFIG_ARMV7_SECURE_RESERVE_SIZE to carve out
such a region. We only support cutting off memory from the beginning or
the end of a RAM bank as we do not want to increase their number (which
would happen if punching a hole) for simplicity reasons
This will be used in a subsequent patch for Jetson-TK1.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Tom Warren <twarren@nvidia.com>
|
| /rk3399_rockchip-uboot/arch/arm/include/asm/ |
| H A D | armv7.h | d6b72da029ab85b344b98b28b12d7cbe800b6cc4 Tue Apr 21 05:18:32 UTC 2015 Jan Kiszka <jan.kiszka@siemens.com> virt-dt: Allow reservation of secure region when in a RAM carveout
In this case the secure code lives in RAM, and hence the memory node in
the device tree needs to be adjusted. This avoids that the OS will map
and possibly access the reservation.
Add support for setting CONFIG_ARMV7_SECURE_RESERVE_SIZE to carve out
such a region. We only support cutting off memory from the beginning or
the end of a RAM bank as we do not want to increase their number (which
would happen if punching a hole) for simplicity reasons
This will be used in a subsequent patch for Jetson-TK1.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Tom Warren <twarren@nvidia.com>
|