From: Andrew F. Davis <afd@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 03/10] arm: mach-omap2: Enable Kconfig support for K2 HS devices
Date: Fri, 7 Apr 2017 10:00:04 -0500 [thread overview]
Message-ID: <20170407150011.5459-4-afd@ti.com> (raw)
In-Reply-To: <20170407150011.5459-1-afd@ti.com>
From: Vitaly Andrianov <vitalya@ti.com>
Like the OMAP54xx, AM43xx, & AM33xx family SoCs, the keystone family
of SoCs also have high security enabled models. Allow K2E devices to
be built with HS Device Type Support.
Signed-off-by: Vitaly Andrianov <vitalya@ti.com>
Signed-off-by: Madan Srinivas <madans@ti.com>
Signed-off-by: Andrew F. Davis <afd@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
---
arch/arm/mach-omap2/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
index 24bc485195..d74b068abc 100644
--- a/arch/arm/mach-omap2/Kconfig
+++ b/arch/arm/mach-omap2/Kconfig
@@ -1,6 +1,6 @@
config TI_SECURE_DEVICE
bool "HS Device Type Support"
- depends on OMAP54XX || AM43XX || AM33XX
+ depends on OMAP54XX || AM43XX || AM33XX || ARCH_KEYSTONE
help
If a high secure (HS) device type is being used, this config
must be set. This option impacts various aspects of the
--
2.11.0
next prev parent reply other threads:[~2017-04-07 15:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 15:00 [U-Boot] [PATCH v2 00/10] Add support for secure boot on Keystone2 SoCs Andrew F. Davis
2017-04-07 15:00 ` [U-Boot] [PATCH v2 01/10] image: Fixes build warning with CONFIG_FIT_IMAGE_POST_PROCESS Andrew F. Davis
2017-04-08 3:55 ` Lokesh Vutla
2017-04-09 19:28 ` Simon Glass
2017-04-10 18:25 ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-04-07 15:00 ` [U-Boot] [PATCH v2 02/10] arm: mach-keystone: Implements FIT post-processing call for keystone SoCs Andrew F. Davis
2017-04-08 3:55 ` Lokesh Vutla
2017-04-10 18:25 ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-04-07 15:00 ` Andrew F. Davis [this message]
2017-04-08 3:55 ` [U-Boot] [PATCH v2 03/10] arm: mach-omap2: Enable Kconfig support for K2 HS devices Lokesh Vutla
2017-04-10 18:25 ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-04-07 15:00 ` [U-Boot] [PATCH v2 04/10] arm: mach-omap2: Add secure image name common to OMAP and keystone Andrew F. Davis
2017-04-08 3:56 ` Lokesh Vutla
2017-04-10 18:25 ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-04-07 15:00 ` [U-Boot] [PATCH v2 05/10] ARM: Keystone2: Build secure images for K2 Andrew F. Davis
2017-04-08 3:58 ` Lokesh Vutla
2017-04-10 18:25 ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-04-07 15:00 ` [U-Boot] [PATCH v2 06/10] doc: Updates info on using Keystone2 secure devices Andrew F. Davis
2017-04-08 3:58 ` Lokesh Vutla
2017-04-10 18:25 ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-04-07 15:00 ` [U-Boot] [PATCH v2 07/10] Kconfig: Adds SYS_TEXT_BASE config option for Keystone2 Andrew F. Davis
2017-04-08 3:58 ` Lokesh Vutla
2017-04-10 18:25 ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-04-07 15:00 ` [U-Boot] [PATCH v2 08/10] defconfig: k2e_hs_evm: Add k2e_hs_evm_defconfig Andrew F. Davis
2017-04-08 3:59 ` Lokesh Vutla
2017-04-10 18:25 ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-04-07 15:00 ` [U-Boot] [PATCH v2 09/10] defconfig: k2hk_hs_evm: Add k2hk_hs_evm_defconfig Andrew F. Davis
2017-04-10 18:25 ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-04-07 15:00 ` [U-Boot] [PATCH v2 10/10] defconfig: k2g_hs_evm: Add k2g_hs_evm_defconfig Andrew F. Davis
2017-04-10 18:25 ` [U-Boot] [U-Boot, v2, " 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=20170407150011.5459-4-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