Searched hist:"7 f0b2e78e0ca4ce686ac632170073f924e34c5a3" (Results 1 – 2 of 2) sorted by relevance
| /rk3399_ARM-atf/plat/rockchip/rk3288/drivers/secure/ |
| H A D | secure.c | 7f0b2e78e0ca4ce686ac632170073f924e34c5a3 Wed Oct 09 12:39:44 UTC 2019 Heiko Stuebner <heiko.stuebner@theobroma-systems.com> rockchip: really use base+size for secure ddr regions
The calls to secure ddr regions on rk3288 and rk3399 use parameters of
base and size - as it custom for specifying memory regions, but the
functions themself expect start and endpoints of the area.
This only works by chance for the TZRAM, as it starts a 0x0 and therefore
its end location is the same as its size.
To not fall into a trap later on adapt the functions to really take
base+size parameters.
Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
Change-Id: Idb9fab38aa081f3335a4eca971e7b7f6757fbbab
|
| /rk3399_ARM-atf/plat/rockchip/rk3399/drivers/secure/ |
| H A D | secure.c | 7f0b2e78e0ca4ce686ac632170073f924e34c5a3 Wed Oct 09 12:39:44 UTC 2019 Heiko Stuebner <heiko.stuebner@theobroma-systems.com> rockchip: really use base+size for secure ddr regions
The calls to secure ddr regions on rk3288 and rk3399 use parameters of
base and size - as it custom for specifying memory regions, but the
functions themself expect start and endpoints of the area.
This only works by chance for the TZRAM, as it starts a 0x0 and therefore
its end location is the same as its size.
To not fall into a trap later on adapt the functions to really take
base+size parameters.
Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
Change-Id: Idb9fab38aa081f3335a4eca971e7b7f6757fbbab
|