From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Dannenberg Date: Wed, 20 Apr 2016 17:48:43 -0500 Subject: [U-Boot] [PATCH 04/16] ti: omap-common: Add Kconfig file for secure device support In-Reply-To: <1460417838-22343-5-git-send-email-d-allred@ti.com> References: <1460417838-22343-1-git-send-email-d-allred@ti.com> <1460417838-22343-5-git-send-email-d-allred@ti.com> Message-ID: <20160420224843.GI16786@borg.dal.design.ti.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, Apr 11, 2016 at 06:37:06PM -0500, Daniel Allred wrote: > From: Madan Srinivas > > 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 > Signed-off-by: Daniel Allred 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 -- Andreas Dannenberg Texas Instruments Inc