From: Gary Bisson <gary.bisson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/5] Add i.MX HAB encryption support
Date: Thu, 25 Aug 2016 19:03:15 +0200 [thread overview]
Message-ID: <1472144600-1834-1-git-send-email-gary.bisson@boundarydevices.com> (raw)
In-Reply-To: <1471989321-25280-1-git-send-email-gary.bisson@boundarydevices.com>
Hi all,
This patch is actually a follow-up of the one from Peng Fan:
https://patchwork.ozlabs.org/patch/616568/
As he mentioned at the time, the current i.MX source code doesn't allow
to build a U-Boot that supports encryption features (dek commands).
The reason is that the commit 2bb01482 did some cleanup, removing usec2ticks
which is mandatory for the Freescale/NXP job ring code to build.
At the time of the original patch, Tom/Stefano said that a configuration
would need to leverage those options and some of the config should be
moved to Kconfig. The goal of this series is to enable it in the common
mx6/7 configuration files.
The series also adds the missing CSF declaration in nitrogen6* cfg files.
Changes v1->v2:
- Simplified the help comment of the SECURE_BOOT config option
- Moved SECURE_BOOT options to mx6/7_common.h
Let me know your thoughts.
Regards,
Gary
Gary Bisson (4):
arm: imx-common: add SECURE_BOOT option to Kconfig
mx6_common: add secure boot support
mx7_common: add secure boot support
nitrogen6x: add secure boot support
Peng Fan (1):
arm: imx-common: introduce back usec2ticks
arch/arm/imx-common/Kconfig | 7 +++++++
arch/arm/imx-common/timer.c | 16 ++++++++++++++++
board/boundary/nitrogen6x/nitrogen6dl.cfg | 3 +++
board/boundary/nitrogen6x/nitrogen6dl2g.cfg | 3 +++
board/boundary/nitrogen6x/nitrogen6q.cfg | 3 +++
board/boundary/nitrogen6x/nitrogen6q2g.cfg | 3 +++
board/boundary/nitrogen6x/nitrogen6s.cfg | 3 +++
board/boundary/nitrogen6x/nitrogen6s1g.cfg | 3 +++
include/configs/colibri_imx7.h | 4 ----
include/configs/mx6_common.h | 9 +++++++++
include/configs/mx7_common.h | 9 +++++++++
include/configs/mx7dsabresd.h | 4 ----
12 files changed, 59 insertions(+), 8 deletions(-)
--
2.8.1
next prev parent reply other threads:[~2016-08-25 17:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 21:55 [U-Boot] [PATCH 0/3] Add i.MX HAB encryption support Gary Bisson
2016-08-23 21:55 ` [U-Boot] [PATCH 1/3] arm: imx-common: add SECURE_BOOT option to Kconfig Gary Bisson
2016-08-24 0:24 ` Eric Nelson
2016-08-24 10:12 ` Gary Bisson
2016-08-24 13:13 ` Eric Nelson
2016-08-23 21:55 ` [U-Boot] [PATCH 2/3] arm: imx-common: introduce back usec2ticks Gary Bisson
2016-08-24 0:30 ` Eric Nelson
2016-08-24 10:15 ` Gary Bisson
2016-08-23 21:55 ` [U-Boot] [PATCH 3/3] nitrogen6x: add secure boot support Gary Bisson
2016-08-24 0:35 ` Eric Nelson
2016-08-24 10:17 ` Gary Bisson
2016-08-25 16:22 ` Fabio Estevam
2016-08-25 17:03 ` Gary Bisson [this message]
2016-08-25 17:03 ` [U-Boot] [PATCH v2 1/5] arm: imx-common: add SECURE_BOOT option to Kconfig Gary Bisson
2016-08-25 17:03 ` [U-Boot] [PATCH v2 2/5] arm: imx-common: introduce back usec2ticks Gary Bisson
2016-08-25 17:03 ` [U-Boot] [PATCH v2 3/5] mx6_common: add secure boot support Gary Bisson
2016-08-25 17:03 ` [U-Boot] [PATCH v2 4/5] mx7_common: " Gary Bisson
2016-08-25 17:03 ` [U-Boot] [PATCH v2 5/5] nitrogen6x: " Gary Bisson
2016-10-17 7:09 ` [U-Boot] [PATCH v2 0/5] Add i.MX HAB encryption support Stefano Babic
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=1472144600-1834-1-git-send-email-gary.bisson@boundarydevices.com \
--to=gary.bisson@boundarydevices.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