Lokesh Vutla adc702e229 arm: K3: Fix usage of CONFIG_SYS_K3_KEY ... For signing the tiboot3.bin image, an optional KEY file can be passed using CONFIG_SYS_K3_KEY. Right now, Makefile scripts directly takes the config value and uses it for signing. This is okay if the build directory is a sub-directory of source tree, otherwise it fails. Fix it by using the path relative to the source tree. Reported-by: Jean-Jacques Hiblot <jjhiblot@ti.com> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>		2018-12-26 21:35:52 -05:00
..
include/mach	ram: Introduce K3 AM654 DDR Sub System driver	2018-11-16 16:51:58 -05:00
Kconfig	armv7R: K3: am654: Add support to start ATF from R5 SPL	2018-11-16 16:51:58 -05:00
Makefile	armv7r: K3: Allow SPL to run only on core 0	2018-11-26 22:52:11 -05:00
am6_init.c	armv7R: K3: am654: Add support for triggering ddr init from SPL	2018-11-16 16:51:59 -05:00
arm64-mmu.c	armv8: K3: am654: Add custom MMU support	2018-09-11 08:32:55 -04:00
common.c	armv7R: K3: am654: Add support to start ATF from R5 SPL	2018-11-16 16:51:58 -05:00
common.h	armv7R: K3: am654: Enable MPU regions	2018-11-16 16:51:58 -05:00
config.mk	arm: K3: Fix usage of CONFIG_SYS_K3_KEY	2018-12-26 21:35:52 -05:00
lowlevel_init.S	armv7r: K3: Allow SPL to run only on core 0	2018-11-26 22:52:11 -05:00
r5_mpu.c	armv7R: K3: am654: Enable MPU regions	2018-11-16 16:51:58 -05:00