summaryrefslogtreecommitdiff
path: root/include/configs/ti_omap5_common.h
diff options
context:
space:
mode:
authorAndrew F. Davis <afd@ti.com>2019-01-17 22:43:05 +0300
committerTom Rini <trini@konsulko.com>2019-01-26 16:13:55 +0300
commit0fd1359c5a9ba79a6bb408859e3376242a513ae2 (patch)
tree0146cc37e8e0f2b3c40c746d80eb1ec9869b272a /include/configs/ti_omap5_common.h
parent2dd468dbe13ceafad23e000d250990c7087206d2 (diff)
downloadu-boot-0fd1359c5a9ba79a6bb408859e3376242a513ae2.tar.xz
ARM: mach-omap2: Kconfig: Allow OMAP5 devices to set entry point
Like AM33xx and AM43xx, DRA7xx and AM57xx devices may need to have an non-standard boot address in memory. This may be due to the device being a high security variant, which place the Initial SoftWare (ISW) after certificates and secure software. Allow these devices to set this from Kconfig. Signed-off-by: Andrew F. Davis <afd@ti.com>
Diffstat (limited to 'include/configs/ti_omap5_common.h')
-rw-r--r--include/configs/ti_omap5_common.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/configs/ti_omap5_common.h b/include/configs/ti_omap5_common.h
index 8bf4a6b7e9..ba57c40182 100644
--- a/include/configs/ti_omap5_common.h
+++ b/include/configs/ti_omap5_common.h
@@ -81,7 +81,7 @@
* RAM from address 0x40301350 (0x40300000+0x1000(reserved)+0x350(cert)).
*/
#define TI_OMAP5_SECURE_BOOT_RESV_SRAM_SZ 0x1000
-#define CONFIG_SPL_TEXT_BASE 0x40301350
+#define CONFIG_SPL_TEXT_BASE CONFIG_ISW_ENTRY_ADDR
/* If no specific start address is specified then the secure EMIF
* region will be placed at the end of the DDR space. In order to prevent
* the main u-boot relocation from clobbering that memory and causing a