From: Sudeep Holla <sudeep.holla@kernel.org>
To: linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Sudeep Holla <sudeep.holla@kernel.org>,
Jamie Nguyen <jamien@nvidia.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Hanjun Guo <guohanjun@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Dat Mach <dmach@nvidia.com>
Subject: [PATCH 0/2] ACPI: Arm FFH: Add support for OpRegion Offset 2 (FF-A DIRECT_REQ2)
Date: Tue, 3 Nov 2026 17:39:05 +0000 [thread overview]
Message-ID: <20261103173907.1996118-1-sudeep.holla@kernel.org> (raw)
Hi,
This patch series extends the existing Linux kernel ACPI Functional Fixed
Hardware (FFH) Operation Region support to accommodate FFH Operation Region
Offset 2, as introduced in the Arm Functional Fixed Hardware Specification
v1.3.
Background
----------
The Arm FFH Specification v1.3 adds support for FFH Operation Region Offset 2.
An OpRegion declared with an offset of 2 triggers an FFA_MSG_SEND_DIRECT_REQ2
call instead of using legacy SMC/HVC or standard DIRECT_REQ variants.
This mechanism allows the platform's ACPI firmware to interact directly
with secure partitions by evaluating a service UUID.
Implementation
--------------
- Upgrades the arm64 low-level FFH handler beyond generic SMCCC calls to
natively support the FF-A protocol. It negotiates FF-A v1.2, identifies
sender endpoints via FFA_ID_GET, translates ACPI ToUUID properties to
register formats, handles interrupted/yielded calls via FFA_RUN, and
returns standard FFH status codes to AML.
- Leverages register-based endpoint discovery (FFA_PARTITION_INFO_GET_REGS)
to resolve unique receivers from service UUIDs. This approach completely
avoids RX/TX memory buffer ownership complexities, keeping the low-level
ACPI FFH subsystem cleanly decoupled from the main Arm FF-A transport
driver.
Sudeep Holla (2):
firmware: arm_ffa: Share FF-A register field definitions
ACPI: FFH: Support FF-A direct request 2 calls
drivers/acpi/arm64/ffh.c | 227 ++++++++++++++++++++++++++++++
drivers/firmware/arm_ffa/driver.c | 48 +++----
include/linux/arm_ffa.h | 19 +++
3 files changed, 263 insertions(+), 31 deletions(-)
--
2.43.0
next reply other threads:[~2026-11-03 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 17:39 Sudeep Holla [this message]
2026-11-03 17:39 ` [PATCH 1/2] firmware: arm_ffa: Share FF-A register field definitions Sudeep Holla
2026-11-03 17:39 ` [PATCH 2/2] ACPI: FFH: Support FF-A direct request 2 calls Sudeep Holla
2026-11-03 21:11 ` Jamie Nguyen
2026-11-04 9:40 ` Sudeep Holla
2026-11-04 17:01 ` Jamie Nguyen
2026-11-03 22:53 ` Jonathan Cameron
2026-11-04 10:19 ` Sudeep Holla
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=20261103173907.1996118-1-sudeep.holla@kernel.org \
--to=sudeep.holla@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dmach@nvidia.com \
--cc=guohanjun@huawei.com \
--cc=jamien@nvidia.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=will@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