Heiko Stuebner 7f0b2e78e0 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		2019-12-17 01:29:07 +01:00
..
dp	rockchip: Prevent macro expansion in paths	2019-12-13 14:13:45 -06:00
dram	Enable -Wshadow always	2019-11-19 08:53:16 -06:00
gpio	Sanitise includes across codebase	2019-01-04 10:43:17 +00:00
m0	rk3399: m0: Fix compiler warnings.	2019-04-24 23:03:10 +02:00
pmu	rockchip: Prevent macro expansion in paths	2019-12-13 14:13:45 -06:00
pwm	Standardise header guards across codebase	2018-11-08 10:20:19 +00:00
secure	rockchip: really use base+size for secure ddr regions	2019-12-17 01:29:07 +01:00
soc	Sanitise includes across codebase	2019-01-04 10:43:17 +00:00