All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] ARM: Kconfig: Move TI_SECURE_DEVICE to a common area
Date: Thu, 15 Feb 2018 11:59:13 +0530	[thread overview]
Message-ID: <eba46d2b-28a1-a2c0-61ad-43a004da82eb@ti.com> (raw)
In-Reply-To: <20180214175339.31459-1-afd@ti.com>



On Wednesday 14 February 2018 11:23 PM, Andrew F. Davis wrote:
> TI_SECURE_DEVICE is used by both OMAP2+ and Keystone2 family devices,
> and so when ARCH_OMAP2PLUS was used to gate off the OMAP2+ Kconfig
> Keystone2 family devices lost this config option.
> 
> Move this option out of mach-omap2 Kconfig to a spot accessible by both
> families. We picked arch/arm/Kconfig over the TI specific board/ti/
> location as this option is not specific to our boards but rather our
> architecture.
> 
> Plus at some point this option can be changed to just
> SECURE_DEVICE, as having secure parts is not exclusive to TI and
> so other vendors can interpret this option as needed by their device
> configurations.
> 
> Fixes: a93fbf4a7892 ("ARM: omap2+: rename config to ARCH_OMAP2PLUS and consolidate Kconfig")
> Signed-off-by: Andrew F. Davis <afd@ti.com>

Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>

Thanks and regards,
Lokesh

> ---
>  arch/arm/Kconfig            | 10 ++++++++++
>  arch/arm/mach-omap2/Kconfig | 10 ----------
>  2 files changed, 10 insertions(+), 10 deletions(-)
> 
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index 7b618d6881..466c7502d5 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -1189,6 +1189,16 @@ config ARCH_ASPEED
>  
>  endchoice
>  
> +config TI_SECURE_DEVICE
> +	bool "HS Device Type Support"
> +	depends on ARCH_KEYSTONE || ARCH_OMAP2PLUS
> +	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/mach-aspeed/Kconfig"
>  
>  source "arch/arm/mach-at91/Kconfig"
> diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
> index abd1aa7fe1..62c25c4044 100644
> --- a/arch/arm/mach-omap2/Kconfig
> +++ b/arch/arm/mach-omap2/Kconfig
> @@ -133,16 +133,6 @@ config SYS_MPUCLK
>  	help
>  	  Defines the MPU clock speed (in MHz).
>  
> -config TI_SECURE_DEVICE
> -	bool "HS Device Type Support"
> -	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
> -	  build system (to create signed boot images that can be
> -	  authenticated) and the code. See the doc/README.ti-secure
> -	  file for further details.
> -
>  config TI_SECURE_EMIF_REGION_START
>  	hex "Reserved EMIF region start address"
>  	depends on TI_SECURE_DEVICE
> 

  parent reply	other threads:[~2018-02-15  6:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 17:53 [U-Boot] [PATCH 1/3] ARM: Kconfig: Move TI_SECURE_DEVICE to a common area Andrew F. Davis
2018-02-14 17:53 ` [U-Boot] [PATCH 2/3] env: Fix missed getenv_ulong to env_get_ulong conversion Andrew F. Davis
2018-02-15  6:29   ` Lokesh Vutla
2018-02-23 18:03   ` [U-Boot] [U-Boot, " Tom Rini
2018-02-14 17:53 ` [U-Boot] [PATCH 3/3] defconfig: k2x_hs_evm: Re-enable TI_SECURE_DEVICE in HS K2x parts Andrew F. Davis
2018-02-15  6:29   ` Lokesh Vutla
2018-02-23 18:03   ` [U-Boot] [U-Boot, " Tom Rini
2018-02-15  6:29 ` Lokesh Vutla [this message]
2018-02-23 18:03 ` [U-Boot] [U-Boot, 1/3] ARM: Kconfig: Move TI_SECURE_DEVICE to a common area 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=eba46d2b-28a1-a2c0-61ad-43a004da82eb@ti.com \
    --to=lokeshvutla@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.