All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/8] boot/arm-trusted-firmware: in-tree and OP-TEE BL32
Date: Wed, 20 Mar 2019 22:54:59 +0100	[thread overview]
Message-ID: <20190320225459.6e46ce9c@windsurf> (raw)
In-Reply-To: <1552951269-16967-2-git-send-email-etienne.carriere@linaro.org>

Hello Etienne,

On Tue, 19 Mar 2019 00:21:03 +0100
Etienne Carriere <etienne.carriere@linaro.org> wrote:

> This change allows one to build trusted firmware (TF-A) with OP-TEE
> as BL32 secure payload.
> 
> When BR2_TARGET_ARM_TRUSTED_FIRMWARE_INTREE_BL32 is enabled TF-A
> builds a BL32 stage according the TF-A configuration directive.
> If these specify no BL3 stage then TF-A will build without BL32
> support. This is the default configuration and reflects TF-A legacy
> integration in BR.
> 
> When BR2_TARGET_ARM_TRUSTED_FIRMWARE_OPTEE_AS_BL32 is enabled
> TF-A builds with support for the OP-TEE OS as BL32.
> 
> Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>

I have applied, after doing a few changes. See below.

> +choice
> +	prompt "Select BL32 stage"

Simplified to just "BL32"

> +config BR2_TARGET_ARM_TRUSTED_FIRMWARE_INTREE_BL32

Changed to:

BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL32_DEFAULT

I found the "in-tree" confusing, because in most cases, it's actually
"no BL32". What this option does is essentially nothing, i.e keeps the default.

> +	bool "Intree or no BL32 stage"

Changed to "Default"

> +	help
> +	  This option shall be set if the BL32 image is built from
> +	  trusted firmware sources (i.e sp_min, tsp) or when no BL32
> +	  is expected.
> +
> +	  When the BL32 stage shall be built from ATF source tree,
> +	  the target BL32 payload shall be defined from configuration
> +	  BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_VARIABLES, either
> +	  using directive SPD=<bl32_id> (Aarch64 platforms,
> +	  i.e SPD=tspd) or AARCH32_SP=<bl32_id> (Aarch32 and Armv7
> +	  platforms, i.e "AARCH32_SP=sp_min"). If no SPD or AARCH32_SP
> +	  directive is specified, ATF will build without BL32 support.

I've reworded this to simplify a bit the explanation.

> +
> +config BR2_TARGET_ARM_TRUSTED_FIRMWARE_OPTEE_AS_BL32

Renamed to BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL32_OPTEE

> +ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_OPTEE_AS_BL32),y)
> +ARM_TRUSTED_FIRMWARE_DEPENDENCIES += optee-os
> +ARM_TRUSTED_FIRMWARE_MAKE_OPTS += BL32=$(BINARIES_DIR)/tee-header_v2.bin
> +ARM_TRUSTED_FIRMWARE_MAKE_OPTS += BL32_EXTRA1=$(BINARIES_DIR)/tee-pager_v2.bin
> +ARM_TRUSTED_FIRMWARE_MAKE_OPTS += BL32_EXTRA2=$(BINARIES_DIR)/tee-pageable_v2.bin

I grouped these definitions in a single assignment to
ARM_TRUSTED_FIRMWARE_MAKE_OPTS.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-03-20 21:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 23:21 [Buildroot] [PATCH v2 1/8] boot/arm-trusted-firmware: support 32bit Arm targets Etienne Carriere
2019-03-18 23:21 ` [Buildroot] [PATCH v2 2/8] boot/arm-trusted-firmware: in-tree and OP-TEE BL32 Etienne Carriere
2019-03-20 21:54   ` Thomas Petazzoni [this message]
2019-03-18 23:21 ` [Buildroot] [PATCH v2 3/8] boot/arm-trusted-firmware: support debug mode Etienne Carriere
2019-03-20 21:59   ` Thomas Petazzoni
2019-03-18 23:21 ` [Buildroot] [PATCH v2 4/8] boot/arm-trusted-firmware: support alternate image files Etienne Carriere
2019-03-20 22:03   ` Thomas Petazzoni
2019-03-21  8:06     ` Etienne Carriere
2019-03-18 23:21 ` [Buildroot] [PATCH v2 5/8] package/optee-test: fix dependency in TAs build Etienne Carriere
2019-03-20 22:03   ` Thomas Petazzoni
2019-03-18 23:21 ` [Buildroot] [PATCH v2 6/8] configs/qemu_armv7a_tz_virt: Armv7-A emulation with TrustZone services Etienne Carriere
2019-03-19 22:00   ` Arnout Vandecappelle
2019-03-20  8:49     ` Etienne Carriere
2019-03-20  9:20       ` Arnout Vandecappelle
2019-03-20 12:06         ` Etienne Carriere
2019-03-18 23:21 ` [Buildroot] [PATCH v2 7/8] testing: test can use the locally generated qemu host tool Etienne Carriere
2019-03-19  7:05   ` Etienne Carriere
2019-03-19 22:03     ` Arnout Vandecappelle
2019-03-22 10:06       ` Etienne Carriere
2019-03-18 23:21 ` [Buildroot] [PATCH v2 8/8] support/testing: test_optee.py: test optee boot and testsuite Etienne Carriere
2019-03-20 21:34 ` [Buildroot] [PATCH v2 1/8] boot/arm-trusted-firmware: support 32bit Arm targets Thomas Petazzoni

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=20190320225459.6e46ce9c@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.