From: Andrew F. Davis <afd@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 10/13] ti: omap-common: Allow AM33xx devices to be built securely
Date: Thu, 18 Aug 2016 10:41:43 -0500 [thread overview]
Message-ID: <20160818154146.16788-11-afd@ti.com> (raw)
In-Reply-To: <20160818154146.16788-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.2
next prev parent reply other threads:[~2016-08-18 15:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 15:41 [U-Boot] [PATCH 00/13] Cleanups to allow secure boot on AM33xx devices Andrew F. Davis
2016-08-18 15:41 ` [U-Boot] [PATCH 01/13] spl: Kconfig: Add SPL_<media>_SUPPORT as Kconfig option Andrew F. Davis
2016-08-19 6:27 ` Heiko Schocher
2016-08-19 19:30 ` Andrew F. Davis
2016-08-19 19:54 ` Tom Rini
2016-08-21 18:35 ` Andrew F. Davis
2016-08-21 18:50 ` Tom Rini
2016-08-21 19:12 ` Andrew F. Davis
2016-08-21 19:33 ` Tom Rini
2016-08-22 14:06 ` Andrew F. Davis
2016-08-18 15:41 ` [U-Boot] [PATCH 02/13] spl: Kconfig: Add SPL_<media>_BOOT " Andrew F. Davis
2016-08-19 4:10 ` Lokesh Vutla
2016-08-19 15:29 ` Andrew F. Davis
2016-08-22 4:23 ` Lokesh Vutla
2016-08-22 12:25 ` Tom Rini
2016-08-22 12:55 ` Simon Glass
2016-08-23 6:15 ` Masahiro Yamada
2016-08-18 15:41 ` [U-Boot] [PATCH 03/13] spl: Kconfig: Add CONFIG_SPL_TEXT_BASE " Andrew F. Davis
2016-08-19 4:12 ` Lokesh Vutla
2016-08-19 12:22 ` Simon Glass
2016-08-18 15:41 ` [U-Boot] [PATCH 04/13] config: am335x_evm: Move CONFIG_SPL_YMODEM_SUPPORT to Kconfig Andrew F. Davis
2016-08-18 15:41 ` [U-Boot] [PATCH 05/13] config: am43xx_evm: " Andrew F. Davis
2016-08-18 15:41 ` [U-Boot] [PATCH 06/13] Kconfig: Separate AM33XX SOC config from target board config Andrew F. Davis
2016-08-19 4:15 ` Lokesh Vutla
2016-08-22 15:26 ` Andrew F. Davis
2016-08-18 15:41 ` [U-Boot] [PATCH 07/13] am33xx: config.mk: Add support for additional secure boot image types Andrew F. Davis
2016-08-18 15:41 ` [U-Boot] [PATCH 08/13] am33xx: config.mk: Fix option used to enable SPI SPL image type Andrew F. Davis
2016-08-18 15:41 ` [U-Boot] [PATCH 09/13] doc: Update info on using AM33xx secure devices from TI Andrew F. Davis
2016-08-18 15:41 ` Andrew F. Davis [this message]
2016-08-18 15:41 ` [U-Boot] [PATCH 11/13] omap: Use SD_BOOT in place of EMMC_BOOT Andrew F. Davis
2016-08-18 15:41 ` [U-Boot] [PATCH 12/13] config: Remove usage of CONFIG_STORAGE_EMMC Andrew F. Davis
2016-08-18 15:41 ` [U-Boot] [PATCH 13/13] board: am33xx-hs: spl: Allow post-processing of FIT image on AM33xx Andrew F. Davis
2016-08-19 6:10 ` [U-Boot] [PATCH 00/13] Cleanups to allow secure boot on AM33xx devices Lokesh Vutla
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=20160818154146.16788-11-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