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 v3 0/4] Use ARM SMC Calling Convention when OP-TEE is available
Date: Mon, 30 Dec 2019 13:50:00 -0500 [thread overview]
Message-ID: <20191230185004.32279-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"
Changes from v2:
- Add HS patch using 'optee_available'
Andrew F. Davis (4):
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
ARM: OMAP2+: sleep43xx: Call secure suspend/resume handlers
arch/arm/mach-omap2/common.h | 2 +-
arch/arm/mach-omap2/io.c | 11 ++++++++
arch/arm/mach-omap2/omap-secure.c | 45 +++++++++++++++++++++++++++++++
arch/arm/mach-omap2/omap-secure.h | 10 +++++++
arch/arm/mach-omap2/omap-smc.S | 6 ++---
arch/arm/mach-omap2/pm33xx-core.c | 17 ++++++++++++
6 files changed, 87 insertions(+), 4 deletions(-)
--
2.17.1
next reply other threads:[~2019-12-30 18:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 18:50 Andrew F. Davis [this message]
2019-12-30 18:50 ` [PATCH v3 1/4] ARM: OMAP2+: Add omap_secure_init callback hook for secure initialization Andrew F. Davis
2019-12-30 18:50 ` [PATCH v3 2/4] ARM: OMAP2+: Introduce check for OP-TEE in omap_secure_init() Andrew F. Davis
2019-12-31 6:32 ` Lokesh Vutla
2019-12-31 14:15 ` Andrew F. Davis
2020-01-02 17:14 ` Tony Lindgren
2020-01-02 17:24 ` Andrew F. Davis
2019-12-30 18:50 ` [PATCH v3 3/4] ARM: OMAP2+: Use ARM SMC Calling Convention when OP-TEE is available Andrew F. Davis
2019-12-30 18:50 ` [PATCH v3 4/4] ARM: OMAP2+: sleep43xx: Call secure suspend/resume handlers Andrew F. Davis
2019-12-31 6:20 ` Lokesh Vutla
2019-12-31 14:17 ` Andrew F. Davis
2020-01-02 5:02 ` Lokesh Vutla
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=20191230185004.32279-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox