[U-Boot] [PATCH 4/7] arm: omap-common: Reuse secure image name between OMAP and keystone

[Madan Srinivas]

As K2 can directly boot u-boot, re-use u-boot_HS_XIP_X-LOADER
as the secure image while booting secure K2 devices. Updates the
comments in the file to reflect this.

Signed-off-by: Madan Srinivas <madans at ti.com>
---

 arch/arm/cpu/armv7/omap-common/config_secure.mk | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/arch/arm/cpu/armv7/omap-common/config_secure.mk b/arch/arm/cpu/armv7/omap-common/config_secure.mk
index 1122439..ae5e8de 100644
--- a/arch/arm/cpu/armv7/omap-common/config_secure.mk
+++ b/arch/arm/cpu/armv7/omap-common/config_secure.mk
@@ -78,7 +78,9 @@ u-boot-spl_HS_SPI_X-LOADER: $(obj)/u-boot-spl.bin
 
 # For supporting single stage XiP QSPI on AM43xx, the image is a full u-boot
 # file, not an SPL. In this case the mkomapsecimg command looks for a
-# u-boot-HS_* prefix
+# u-boot-HS_* prefix. Keystone devices also support a single stage boot
+# so this image can be used for booting from all media on keystone
+# secure devices
 u-boot_HS_XIP_X-LOADER: $(obj)/u-boot.bin
 	$(call if_changed,mkomapsecimg)
 
-- 
2.7.4