From: Jens Wiklander <jens.wiklander@linaro.org>
To: arm@kernel.org, soc@kernel.org
Cc: op-tee@lists.trustedfirmware.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sumit Garg <sumit.garg@linaro.org>,
Etienne Carriere <etienne.carriere@linaro.org>
Subject: [GIT PULL] OP-TEE per-cpu irq for v6.4.
Date: Tue, 4 Apr 2023 08:27:27 +0200 [thread overview]
Message-ID: <20230404062727.GA2765560@rayden> (raw)
Hello arm-soc maintainers,
Please pull these patches which add support for using per-cpu interrutps
to signal asynchronous notifications from OP-TEE in secure world to the
OP-TEE driver.
Thanks,
Jens
The following changes since commit eeac8ede17557680855031c6f305ece2378af326:
Linux 6.3-rc2 (2023-03-12 16:36:44 -0700)
are available in the Git repository at:
https://git.linaro.org/people/jens.wiklander/linux-tee.git/ tags/optee-per-cpu-irq-for-v6.4
for you to fetch changes up to b3b4ced12c1bc829888803ce07fff317e590ec1c:
optee: add per cpu asynchronous notification (2023-03-30 08:27:05 +0200)
----------------------------------------------------------------
Add OP-TEE per cpu asynchronous notification
Adds support for signalling from secure world with per-cpu interrupts in
addition to edge-triggered peripheral interrupts.
----------------------------------------------------------------
Etienne Carriere (2):
dt-bindings: optee driver interrupt can be a per-cpu interrupt
optee: add per cpu asynchronous notification
.../bindings/arm/firmware/linaro,optee-tz.yaml | 3 +-
drivers/tee/optee/optee_private.h | 24 ++++
drivers/tee/optee/smc_abi.c | 122 ++++++++++++++++++++-
3 files changed, 144 insertions(+), 5 deletions(-)
next reply other threads:[~2023-04-04 6:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 6:27 Jens Wiklander [this message]
2023-04-04 14:41 ` [GIT PULL] OP-TEE per-cpu irq for v6.4 patchwork-bot+linux-soc
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=20230404062727.GA2765560@rayden \
--to=jens.wiklander@linaro.org \
--cc=arm@kernel.org \
--cc=etienne.carriere@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=soc@kernel.org \
--cc=sumit.garg@linaro.org \
/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