From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/5][v2] armv8/ls1043ardb: SECURE BOOT target added for NOR
Date: Wed, 2 Dec 2015 11:03:31 -0800 [thread overview]
Message-ID: <565F4083.30103@freescale.com> (raw)
In-Reply-To: <1447911713-28639-4-git-send-email-aneesh.bansal@freescale.com>
Add folks familiar with DSPI.
On 11/18/2015 09:41 PM, Aneesh Bansal wrote:
> LS1043ARDB Secure Boot Target from NOR has been added.
> - Configs defined to enable esbc_validate.
> - ESBC Address in header is made 64 bit.
> - SMMU is re-configured in Bypass mode.
>
> Signed-off-by: Aneesh Bansal <aneesh.bansal@freescale.com>
> ---
> Changes in v2:
> New Patch Set created with an additional patch.
> Pointers typecasted to uintptr_t to remove compiler warnings
>
> arch/arm/include/asm/arch-fsl-layerscape/config.h | 16 ++++++++--
> .../include/asm/arch-fsl-layerscape/immap_lsch2.h | 2 +-
> board/freescale/common/fsl_validate.c | 35 +++++++++++++---------
> board/freescale/ls1043ardb/MAINTAINERS | 5 ++++
> board/freescale/ls1043ardb/ls1043ardb.c | 18 ++++++++++-
> common/cmd_blob.c | 6 ++--
> configs/ls1043ardb_SECURE_BOOT_defconfig | 4 +++
> include/configs/ls1043ardb.h | 12 ++++++++
> include/fsl_validate.h | 9 +++++-
> 9 files changed, 85 insertions(+), 22 deletions(-)
> create mode 100644 configs/ls1043ardb_SECURE_BOOT_defconfig
I know a recent change requires CONFIG_SYS_NS16550=y. I am not sure if DSPI
can/should be enabled. Let's wait for Alison/Prabhakar's comment on DSPI.
Alison/Prabhakar, DSPI support is enabled using DM for QDS and RDB for NOR boot.
Do we want to enable DSPI for nand boot, and secure boot?
<snip>
> diff --git a/include/configs/ls1043ardb.h b/include/configs/ls1043ardb.h
> index 307d947..bf3a1a0 100644
> --- a/include/configs/ls1043ardb.h
> +++ b/include/configs/ls1043ardb.h
> @@ -268,4 +268,16 @@
> #define CONFIG_ETHPRIME "FM1 at DTSEC3"
> #endif
>
> +#ifdef CONFIG_SECURE_BOOT
> +/* Hash command with SHA acceleration supported in hardware */
> +#define CONFIG_CMD_HASH
> +#define CONFIG_SHA_HW_ACCEL
> +#define CONFIG_CMD_BLOB
> +
> +/* For LS1043 (ARMv8), ESBC image Address in Header is 64 bit */
> +#define CONFIG_ESBC_ADDR_64BIT
> +
> +#include <asm/fsl_secure_boot.h>
> +#endif
Do you want to put this include inside ifdef? You have both ways in different
header files.
York
next prev parent reply other threads:[~2015-12-02 19:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 5:41 [U-Boot] [PATCH 1/5][v2] armv8: usec2ticks function defined Aneesh Bansal
2015-11-19 5:41 ` [U-Boot] [PATCH 2/5][v2] armv8: Make SEC read/write as snoopable for LS1043 Aneesh Bansal
2015-11-19 5:41 ` [U-Boot] [PATCH 3/5] Data type defined for pointer addresses Aneesh Bansal
2015-12-07 16:50 ` York Sun
2015-12-07 17:02 ` Bansal Aneesh
2015-12-07 17:08 ` Tom Rini
2015-12-07 17:14 ` Scott Wood
2015-12-07 17:33 ` York Sun
2015-12-07 17:50 ` Tom Rini
2015-12-07 20:31 ` York Sun
2015-11-19 5:41 ` [U-Boot] [PATCH 4/5][v2] armv8/ls1043ardb: SECURE BOOT target added for NOR Aneesh Bansal
2015-12-02 19:03 ` York Sun [this message]
2015-11-19 5:41 ` [U-Boot] [PATCH 5/5][v2] drivers/crypto/fsl: fix endianness issue in RNG Aneesh Bansal
2015-11-19 16:56 ` [U-Boot] [PATCH 1/5][v2] armv8: usec2ticks function defined York Sun
2015-11-23 18:50 ` Bansal Aneesh
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=565F4083.30103@freescale.com \
--to=yorksun@freescale.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.