public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andrew F. Davis <afd@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot]  [PATCH v2 0/6] AM43xx OP-TEE support
Date: Mon, 10 Jul 2017 14:45:48 -0500	[thread overview]
Message-ID: <20170710194554.23430-1-afd@ti.com> (raw)

Hello all,

This series brings our firewall and OP-TEE support from DRA7xx/AM57xx
family devices to the AM43xx class devices. We do this by factoring
out code common code from omap5/ into common mach-omap2/ sources. Then
add the hooks for the AM43xx boards.

Thanks,
Andrew

Changes from v1:
 - Stop format-patch from thinking the first patch is a rename
 - Rebase on latest master

Andrew F. Davis (6):
  arm: mach-omap2: Move omap5/sec-fxns.c into sec-common.c
  arm: mach-omap2: Factor out common FDT fixup suport
  arm: mach-omap2: fdt-common: Add OP-TEE node when firmware node is
    defined
  arm: mach-omap2: am33xx: Add FDT fixup suport for AM33xx/AM43xx boards
  board: ti: am43xx: Add TEE loading and firewall setup
  board: ti: am43xx: Add FDT fixup for HS devices

 arch/arm/include/asm/omap_common.h     |   5 +
 arch/arm/include/asm/omap_sec_common.h |   6 +
 arch/arm/mach-omap2/Kconfig            |  26 ++++
 arch/arm/mach-omap2/Makefile           |   2 +
 arch/arm/mach-omap2/am33xx/Makefile    |   1 +
 arch/arm/mach-omap2/am33xx/fdt.c       |  43 ++++++
 arch/arm/mach-omap2/fdt-common.c       | 168 +++++++++++++++++++++++
 arch/arm/mach-omap2/omap5/Kconfig      |  26 ----
 arch/arm/mach-omap2/omap5/Makefile     |   1 -
 arch/arm/mach-omap2/omap5/fdt.c        | 119 -----------------
 arch/arm/mach-omap2/omap5/sec-fxns.c   | 234 ---------------------------------
 arch/arm/mach-omap2/sec-common.c       | 226 ++++++++++++++++++++++++++++++-
 board/ti/am43xx/board.c                |  16 +++
 configs/am43xx_hs_evm_defconfig        |   4 +
 14 files changed, 496 insertions(+), 381 deletions(-)
 create mode 100644 arch/arm/mach-omap2/am33xx/fdt.c
 create mode 100644 arch/arm/mach-omap2/fdt-common.c
 delete mode 100644 arch/arm/mach-omap2/omap5/sec-fxns.c

-- 
2.13.0

             reply	other threads:[~2017-07-10 19:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 19:45 Andrew F. Davis [this message]
2017-07-10 19:45 ` [U-Boot] [PATCH v2 1/6] arm: mach-omap2: Move omap5/sec-fxns.c into sec-common.c Andrew F. Davis
2017-07-25  0:42   ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-07-10 19:45 ` [U-Boot] [PATCH v2 2/6] arm: mach-omap2: Factor out common FDT fixup suport Andrew F. Davis
2017-07-25  0:42   ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-07-10 19:45 ` [U-Boot] [PATCH v2 3/6] arm: mach-omap2: fdt-common: Add OP-TEE node when firmware node is defined Andrew F. Davis
2017-07-25  0:42   ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-07-10 19:45 ` [U-Boot] [PATCH v2 4/6] arm: mach-omap2: am33xx: Add FDT fixup suport for AM33xx/AM43xx boards Andrew F. Davis
2017-07-25  0:42   ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-07-10 19:45 ` [U-Boot] [PATCH v2 5/6] board: ti: am43xx: Add TEE loading and firewall setup Andrew F. Davis
2017-07-25  0:43   ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-07-10 19:45 ` [U-Boot] [PATCH v2 6/6] board: ti: am43xx: Add FDT fixup for HS devices Andrew F. Davis
2017-07-25  0:43   ` [U-Boot] [U-Boot, v2, " Tom Rini
2017-07-10 19:48 ` [U-Boot] [PATCH v2 0/6] AM43xx OP-TEE support Andrew F. Davis

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=20170710194554.23430-1-afd@ti.com \
    --to=afd@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