From: "Andrew F. Davis" <afd@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: <linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Andrew F . Davis" <afd@ti.com>
Subject: [PATCH v2 0/3] Use ARM SMC Calling Convention when OP-TEE is available
Date: Tue, 17 Dec 2019 18:47:42 -0500 [thread overview]
Message-ID: <20191217234745.4434-1-afd@ti.com> (raw)
Hello all,
This is the reworked patch turned into a series to allow upstream kernels
to make use of OP-TEE on the OMAP2+ platform.
Thanks,
Andrew
Changes from v1:
- Split into logical patches
- Check for OP-TEE in DT only once
- Check the OP-TEE node is "okay"
Andrew F. Davis (3):
ARM: OMAP2+: Add omap_secure_init callback hook for secure
initialization
ARM: OMAP2+: Introduce check for OP-TEE in omap_secure_init()
ARM: OMAP2+: Use ARM SMC Calling Convention when OP-TEE is available
arch/arm/mach-omap2/common.h | 2 +-
arch/arm/mach-omap2/io.c | 11 +++++++++
arch/arm/mach-omap2/omap-secure.c | 41 +++++++++++++++++++++++++++++++
arch/arm/mach-omap2/omap-secure.h | 6 +++++
arch/arm/mach-omap2/omap-smc.S | 6 ++---
5 files changed, 62 insertions(+), 4 deletions(-)
--
2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: "Andrew F. Davis" <afd@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
"Andrew F . Davis" <afd@ti.com>
Subject: [PATCH v2 0/3] Use ARM SMC Calling Convention when OP-TEE is available
Date: Tue, 17 Dec 2019 18:47:42 -0500 [thread overview]
Message-ID: <20191217234745.4434-1-afd@ti.com> (raw)
Hello all,
This is the reworked patch turned into a series to allow upstream kernels
to make use of OP-TEE on the OMAP2+ platform.
Thanks,
Andrew
Changes from v1:
- Split into logical patches
- Check for OP-TEE in DT only once
- Check the OP-TEE node is "okay"
Andrew F. Davis (3):
ARM: OMAP2+: Add omap_secure_init callback hook for secure
initialization
ARM: OMAP2+: Introduce check for OP-TEE in omap_secure_init()
ARM: OMAP2+: Use ARM SMC Calling Convention when OP-TEE is available
arch/arm/mach-omap2/common.h | 2 +-
arch/arm/mach-omap2/io.c | 11 +++++++++
arch/arm/mach-omap2/omap-secure.c | 41 +++++++++++++++++++++++++++++++
arch/arm/mach-omap2/omap-secure.h | 6 +++++
arch/arm/mach-omap2/omap-smc.S | 6 ++---
5 files changed, 62 insertions(+), 4 deletions(-)
--
2.17.1
next reply other threads:[~2019-12-17 23:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 23:47 Andrew F. Davis [this message]
2019-12-17 23:47 ` [PATCH v2 0/3] Use ARM SMC Calling Convention when OP-TEE is available Andrew F. Davis
2019-12-17 23:47 ` [PATCH v2 1/3] ARM: OMAP2+: Add omap_secure_init callback hook for secure initialization Andrew F. Davis
2019-12-17 23:47 ` Andrew F. Davis
2019-12-17 23:47 ` [PATCH v2 2/3] ARM: OMAP2+: Introduce check for OP-TEE in omap_secure_init() Andrew F. Davis
2019-12-17 23:47 ` Andrew F. Davis
2019-12-18 0:53 ` Tony Lindgren
2019-12-18 1:00 ` Andrew F. Davis
2019-12-18 1:00 ` Andrew F. Davis
2019-12-30 17:36 ` Tony Lindgren
2019-12-30 18:40 ` Andrew F. Davis
2019-12-30 18:40 ` Andrew F. Davis
2019-12-17 23:47 ` [PATCH v2 3/3] ARM: OMAP2+: Use ARM SMC Calling Convention when OP-TEE is available Andrew F. Davis
2019-12-17 23:47 ` 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=20191217234745.4434-1-afd@ti.com \
--to=afd@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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.