From: Andrew F. Davis <afd@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 05/11] ti: omap-common: Allow AM33xx devices to be built securely
Date: Mon, 22 Aug 2016 10:21:25 -0500 [thread overview]
Message-ID: <20160822152131.15340-6-afd@ti.com> (raw)
In-Reply-To: <20160822152131.15340-1-afd@ti.com>
Like OMAP54xx and AM43xx family SoCs, AM33xx based SoCs have high
security enabled models. Allow AM33xx devices to be built with
HS Device Type Support.
Signed-off-by: Andrew F. Davis <afd@ti.com>
---
arch/arm/cpu/armv7/omap-common/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/cpu/armv7/omap-common/Kconfig b/arch/arm/cpu/armv7/omap-common/Kconfig
index 7b39506..4daccd9 100644
--- a/arch/arm/cpu/armv7/omap-common/Kconfig
+++ b/arch/arm/cpu/armv7/omap-common/Kconfig
@@ -1,6 +1,6 @@
config TI_SECURE_DEVICE
bool "HS Device Type Support"
- depends on OMAP54XX || AM43XX
+ depends on OMAP54XX || AM43XX || AM33XX
help
If a high secure (HS) device type is being used, this config
must be set. This option impacts various aspects of the
--
2.9.3
next prev parent reply other threads:[~2016-08-22 15:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 15:21 [U-Boot] [PATCH v2 00/11] Allow secure boot on AM33xx devices Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [PATCH v2 01/11] Kconfig: Separate AM33XX SOC config from target board config Andrew F. Davis
2016-08-26 20:12 ` Tom Rini
2016-08-22 15:21 ` [U-Boot] [PATCH v2 02/11] am33xx: config.mk: Add support for additional secure boot image types Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [PATCH v2 03/11] am33xx: config.mk: Fix option used to enable SPI SPL image type Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [PATCH v2 04/11] doc: Update info on using AM33xx secure devices from TI Andrew F. Davis
2016-08-22 15:21 ` Andrew F. Davis [this message]
2016-08-22 15:21 ` [U-Boot] [PATCH v2 06/11] board: am33xx-hs: spl: Allow post-processing of FIT image on AM33xx Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [RFC PATCH v2 07/11] omap: Use SD_BOOT in place of EMMC_BOOT Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [RFC PATCH v2 08/11] config: Remove usage of CONFIG_STORAGE_EMMC Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [RFC PATCH v2 09/11] spl: Kconfig: Add SPL_<media>_SUPPORT as Kconfig option Andrew F. Davis
2016-08-23 6:08 ` Masahiro Yamada
2016-08-23 15:02 ` Andrew F. Davis
2016-08-26 20:06 ` Tom Rini
2016-08-22 15:21 ` [U-Boot] [RFC PATCH v2 10/11] spl: Kconfig: Add SPL_<media>_BOOT " Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [RFC PATCH v2 11/11] spl: Kconfig: Add CONFIG_SPL_TEXT_BASE " Andrew F. Davis
2016-08-23 5:45 ` Masahiro Yamada
2016-08-23 14:57 ` Andrew F. Davis
2016-08-26 17:59 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160822152131.15340-6-afd@ti.com \
--to=afd@ti.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox