[U-Boot] [PATCH v3 3/7] arm: omap-common: adds secure image name common to, OMAP and keystone

[Srinivas, Madan]

As K2 can directly boot u-boot, add u-boot_HS_MLO as the
secure image while booting secure K2 devicesr, for all
boot modes other than SPI flash.

Signed-off-by: Madan Srinivas <madans at ti.com>
Reviewed-by: Tom Rini <trini at konsulko.com>

---

Changes in v3: None
Changes in v2:
- Adds a new name for the signed output image in config_secure.mk
   to keep it in line with the image name used by non-secure keystone
   devices.

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

diff --git a/arch/arm/cpu/armv7/omap-common/config_secure.mk 
b/arch/arm/cpu/armv7/omap-common/config_secure.mk
index 1122439..0ece3f8 100644
--- a/arch/arm/cpu/armv7/omap-common/config_secure.mk
+++ b/arch/arm/cpu/armv7/omap-common/config_secure.mk
@@ -76,6 +76,12 @@ u-boot-spl_HS_ISSW: $(obj)/u-boot-spl.bin
  u-boot-spl_HS_SPI_X-LOADER: $(obj)/u-boot-spl.bin
  	$(call if_changed,mkomapsecimg)

+# For supporting single stage boot on keystone, the image is a full u-boot
+# file, not an SPL. This will work for all boot devices, other than SPI
+# flash
+u-boot_HS_MLO: $(obj)/u-boot.bin
+	$(call if_changed,mkomapsecimg)
+
  # 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
-- 
2.7.4