From: Jamie Nguyen <jamien@nvidia.com>
To: Sudeep Holla <sudeep.holla@kernel.org>
Cc: 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>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Dat Mach <dmach@nvidia.com>,
<linux-acpi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] ACPI: arm64: FFH Operation Region support for FF-A (offset 2)
Date: Thu, 24 Sep 2026 08:23:21 -0700 [thread overview]
Message-ID: <20260924152321.3864148-1-jamien@nvidia.com> (raw)
In-Reply-To: <20260924-tall-oryx-of-attraction-23ada5@sudeepholla>
On Thu, Sep 24, 2026 at 10:39:24AM +0100, Sudeep Holla wrote:
> Which version of FF-A is being deployed on your platforms?
We have platforms with FF-A firmware versions 1.1, 1.2 and 1.3. The
platform I have been using to test offset 2 reports FF-A 1.3.
next prev parent reply other threads:[~2026-09-24 15:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 19:29 Jamie Nguyen
2026-09-01 19:29 ` [PATCH v2 1/3] firmware: arm_ffa: Split the response out of ffa_msg_send_direct_req2() Jamie Nguyen
2026-09-21 9:41 ` Hanjun Guo
2026-09-21 17:49 ` Jamie Nguyen
2026-09-22 1:49 ` Hanjun Guo
2026-09-01 19:29 ` [PATCH v2 2/3] ACPI: arm64: Add support for the FF-A FFH Operation Region (offset 2) Jamie Nguyen
2026-09-21 9:54 ` Hanjun Guo
2026-09-21 17:49 ` Jamie Nguyen
2026-09-01 19:29 ` [PATCH v2 3/3] firmware: arm_ffa: Back the ACPI FF-A FFH Operation Region Jamie Nguyen
2026-09-18 16:14 ` [PATCH v2 0/3] ACPI: arm64: FFH Operation Region support for FF-A (offset 2) Jamie Nguyen
2026-09-22 8:46 ` Sudeep Holla
2026-09-22 15:52 ` Jamie Nguyen
2026-09-22 18:06 ` Sudeep Holla
2026-09-23 12:40 ` Jamie Nguyen
2026-09-23 13:38 ` Sudeep Holla
2026-09-23 17:32 ` Jamie Nguyen
2026-09-24 9:39 ` Sudeep Holla
2026-09-24 15:23 ` Jamie Nguyen [this message]
2026-09-24 16:07 ` 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=20260924152321.3864148-1-jamien@nvidia.com \
--to=jamien@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=dmach@nvidia.com \
--cc=guohanjun@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=rafael@kernel.org \
--cc=sudeep.holla@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
all inboxes | Powered by JetHome®