From: Daniel Allred <d-allred@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 04/15] ti: omap-common: Add Kconfig file for secure device support
Date: Thu, 19 May 2016 19:10:44 -0500 [thread overview]
Message-ID: <1463703055-17484-5-git-send-email-d-allred@ti.com> (raw)
In-Reply-To: <1463703055-17484-1-git-send-email-d-allred@ti.com>
From: Madan Srinivas <madans@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 <madans@ti.com>
Signed-off-by: Daniel Allred <d-allred@ti.com>
Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
Tested-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
---
V3:
None
V2:
None
arch/arm/Kconfig | 8 +-------
arch/arm/cpu/armv7/omap-common/Kconfig | 17 +++++++++++++++++
2 files changed, 18 insertions(+), 7 deletions(-)
create mode 100644 arch/arm/cpu/armv7/omap-common/Kconfig
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 6577572..3c545f0 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -776,13 +776,7 @@ source "arch/arm/cpu/armv7/mx6/Kconfig"
source "arch/arm/cpu/armv7/mx5/Kconfig"
-source "arch/arm/cpu/armv7/omap3/Kconfig"
-
-source "arch/arm/cpu/armv7/omap4/Kconfig"
-
-source "arch/arm/cpu/armv7/omap5/Kconfig"
-
-source "arch/arm/cpu/armv7/am33xx/Kconfig"
+source "arch/arm/cpu/armv7/omap-common/Kconfig"
source "arch/arm/mach-orion5x/Kconfig"
diff --git a/arch/arm/cpu/armv7/omap-common/Kconfig b/arch/arm/cpu/armv7/omap-common/Kconfig
new file mode 100644
index 0000000..7b39506
--- /dev/null
+++ b/arch/arm/cpu/armv7/omap-common/Kconfig
@@ -0,0 +1,17 @@
+config TI_SECURE_DEVICE
+ bool "HS Device Type Support"
+ depends on OMAP54XX || AM43XX
+ help
+ If a high secure (HS) device type is being used, this config
+ must be set. This option impacts various aspects of the
+ build system (to create signed boot images that can be
+ authenticated) and the code. See the doc/README.ti-secure
+ file for further details.
+
+source "arch/arm/cpu/armv7/omap3/Kconfig"
+
+source "arch/arm/cpu/armv7/omap4/Kconfig"
+
+source "arch/arm/cpu/armv7/omap5/Kconfig"
+
+source "arch/arm/cpu/armv7/am33xx/Kconfig"
--
1.9.1
next prev parent reply other threads:[~2016-05-20 0:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 0:10 [U-Boot] [PATCH v3 00/15] Support for boot image creation for TI secure devices Daniel Allred
2016-05-20 0:10 ` [U-Boot] [PATCH v3 01/15] doc: Add info on using secure devices from TI Daniel Allred
2016-05-30 18:07 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20 0:10 ` [U-Boot] [PATCH v3 02/15] arm: am33xx: Kconfig: Add secure device definitions Daniel Allred
2016-05-30 18:01 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20 0:10 ` [U-Boot] [PATCH v3 03/15] arm: Kconfig: Add support for AM43xx SoC specific Kconfig Daniel Allred
2016-05-30 18:01 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20 0:10 ` Daniel Allred [this message]
2016-05-30 18:01 ` [U-Boot] [U-Boot, v3, 04/15] ti: omap-common: Add Kconfig file for secure device support Tom Rini
2016-05-20 0:10 ` [U-Boot] [PATCH v3 05/15] ti: omap-common: Add commands for generating secure SPL images Daniel Allred
2016-05-30 18:02 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20 0:10 ` [U-Boot] [PATCH v3 06/15] ti: AM43xx: config.mk: Add support for generating secure boot images Daniel Allred
2016-05-30 18:02 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-30 18:02 ` Tom Rini
2016-05-20 0:10 ` [U-Boot] [PATCH v3 07/15] ti: AM43xx: Use CONFIG options from SOC Kconfig Daniel Allred
2016-05-30 18:02 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20 0:10 ` [U-Boot] [PATCH v3 08/15] ti: AM43xx: board: Detect AM43xx HS EVM Daniel Allred
2016-05-30 18:02 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20 0:10 ` [U-Boot] [PATCH v3 09/15] defconfig: Add a config for AM43xx secure part Daniel Allred
2016-05-30 18:02 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20 0:10 ` [U-Boot] [PATCH v3 10/15] ti_omap5_common: Update SPL start address on secure parts Daniel Allred
2016-05-20 13:02 ` Tom Rini
2016-05-30 18:02 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20 0:10 ` [U-Boot] [PATCH v3 11/15] spl: build: ti: add support for secure boot images Daniel Allred
2016-05-30 18:02 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20 0:10 ` [U-Boot] [PATCH v3 12/15] ARM: omap-common: Add device type to CPU string Daniel Allred
2016-05-30 18:02 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20 0:10 ` [U-Boot] [PATCH v3 13/15] ARM: omap5: add hooks for cpu/SoC fdt fixups Daniel Allred
2016-05-30 18:02 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20 0:10 ` [U-Boot] [PATCH v3 14/15] ARM: omap5: add ft_board_setup for dra7xx/am57xx Daniel Allred
2016-05-30 18:02 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20 0:10 ` [U-Boot] [PATCH v3 15/15] defconfig: ti: Add configs for OMAP5-class secure parts Daniel Allred
2016-05-30 18:03 ` [U-Boot] [U-Boot, v3, " 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=1463703055-17484-5-git-send-email-d-allred@ti.com \
--to=d-allred@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