On Mon, Apr 11, 2016 at 06:37:06PM -0500, Daniel Allred wrote: > From: Madan Srinivas <mad...@ti.com> > > Defines CONFIG_TI_SECURE_DEVICE which needs to be turned on > when building images for secure devices. This flag is used > to invoke the secure image creation tools for creating a > boot image that can be used on secure devices. This flag > may also be used to conditionally compile code specific > to secure devices. > > This terminology will be used by all OMAP architecture devices, > hence introducing to a common location. > > With the creation of Kconfig for omap-common, moved the > sourcing of the Kconfig files for the omap3/4/5 and am33xx > devices from arch/arm/KConfig to the omap-common one. > > Signed-off-by: Madan Srinivas <mad...@ti.com> > Signed-off-by: Daniel Allred <d-all...@ti.com>
Now that I've successfully boot-tested the patch series on actual AM437x HS, DRA72x HS, and DRA74x HS hardware this common file gets my... Tested-by: Andreas Dannenberg <dannenb...@ti.com> -- Andreas Dannenberg Texas Instruments Inc _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot