From: Sudeep Holla <sudeep.holla@arm.com>
To: ARM SoC Team <arm@kernel.org>, SoC Team <soc@kernel.org>,
ALKML <linux-arm-kernel@lists.infradead.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Arnd Bergmann <arnd@kernel.org>, Olof Johansson <olof@lixom.net>
Subject: [GIT PULL] firmware: arm_ffa: Updates for v6.10
Date: Fri, 26 Apr 2024 11:50:48 +0100 [thread overview]
Message-ID: <20240426105051.1527016-1-sudeep.holla@arm.com> (raw)
Hi ARM SoC Team,
Please pull !
Regards,
Sudeep
-->8
The following changes since commit 4cece764965020c22cff7665b18a012006359095:
Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/ffa-updates-6.10
for you to fetch changes up to 3a3e2b83e8059679e92be4273c601ea21e105a89:
firmware: arm_ffa: Avoid queuing work when running on the worker queue (2024-04-25 12:27:55 +0100)
----------------------------------------------------------------
Arm FF-A updates for v6.10
1. Support for handling notification pending interrupt(NPI)
The FF-A uses the notification pending interrupt to inform the receiver
that it has a pending notification. This is a virtual interrupt and is
used by the following type of receivers:
- A guest/VM running under a hypervisor(normal world usecase)
- An S-EL1 SP running under a S-EL2 SPMC(secure world only usecase)
Also, when the FF-A driver is running inside a guest VM under an
hypervisor, the driver/guest VM doesn't have the permission/capability
to request the creation of notification bitmaps. For a VM, the hypervisor
reserves memory for its VM and hypervisor framework notification bitmaps
and the SPMC reserves memory for its SP and SPMC framework notification
bitmaps before the hypervisor initializes it.
These changes include skipping of creation of notification bitmaps, some
refactoring around schedule receiver interrupt(SRI) handling and addition
of support for NPI.
2. Support for FF-A indirect messaging
The FFA_MSG_SEND2 can be used to transmit a partition message from
the Tx buffer of the sender(the driver in this case) endpoint to the Rx
buffer of the receiver endpoint and inform the scheduler that the
receiver endpoint must be run.
Apart from these two main features, there is an optimisation to avoid
queuing of a work when already running on the worker queue.
----------------------------------------------------------------
Dan Carpenter (1):
firmware: arm_ffa: Fix memory corruption in ffa_msg_send2()
Jens Wiklander (2):
firmware: arm_ffa: Skip creation of the notification bitmaps
firmware: arm_ffa: Add support for handling notification pending interrupt(NPI)
Sudeep Holla (5):
firmware: arm_ffa: Refactor SRI handling in prepartion to add NPI support
firmware: arm_ffa: Fix kernel warning about incorrect SRI/NPI
firmware: arm_ffa: Stash the partition properties for query purposes
firmware: arm_ffa: Add support for FFA_MSG_SEND2
firmware: arm_ffa: Avoid queuing work when running on the worker queue
drivers/firmware/arm_ffa/driver.c | 187 +++++++++++++++++++++++++++++---------
include/linux/arm_ffa.h | 27 ++++++
2 files changed, 169 insertions(+), 45 deletions(-)
next reply other threads:[~2024-04-26 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 10:50 Sudeep Holla [this message]
2024-04-29 21:00 ` [GIT PULL] firmware: arm_ffa: Updates for v6.10 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=20240426105051.1527016-1-sudeep.holla@arm.com \
--to=sudeep.holla@arm.com \
--cc=arm@kernel.org \
--cc=arnd@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=soc@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).