From: Jamie Nguyen <jamien@nvidia.com>
To: Sudeep Holla <sudeep.holla@kernel.org>
Cc: <linux-acpi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
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: Re: [PATCH v2 0/3] ACPI: Arm FFH: Add support for OpRegion Offset 2 (FF-A DIRECT_REQ2)
Date: Fri, 13 Nov 2026 09:35:22 -0800 [thread overview]
Message-ID: <20261113173522.1544082-1-jamien@nvidia.com> (raw)
In-Reply-To: <20261112-acpi_ffh_ffa-v2-0-575a9dbed22b@kernel.org>
Tested on an NVIDIA platform (FF-A v1.3) with firmware that uses
offset 2. TPM PPI fails without this series and works with it, both
with and without patch 3. Without patch 3, the second FFA_VERSION
from ffh.c just got v1.3 back from the SPMC.
If you decide to keep patch 3, then the kernel test robot warnings
[1][2] ought to be fixed in a v3.
For the series:
Tested-by: Jamie Nguyen <jamien@nvidia.com>
[1] https://lore.kernel.org/all/202611131010.OMo0VbqM-lkp@intel.com/
[2] https://lore.kernel.org/all/202611131749.3XbZQkPM-lkp@intel.com/
prev parent reply other threads:[~2026-11-13 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 11:14 [PATCH v2 0/3] ACPI: Arm FFH: Add support for OpRegion Offset 2 (FF-A DIRECT_REQ2) Sudeep Holla
2026-11-12 11:14 ` [PATCH v2 1/3] firmware: arm_ffa: Share FF-A register field definitions Sudeep Holla
2026-11-12 11:14 ` [PATCH v2 2/3] ACPI: FFH: Support FF-A direct request 2 calls Sudeep Holla
2026-11-12 11:14 ` [PATCH v2 3/3] firmware: arm_ffa: Share FF-A version negotiation Sudeep Holla
2026-11-12 16:30 ` Jamie Nguyen
2026-11-13 9:38 ` Sudeep Holla
2026-11-13 2:50 ` kernel test robot
2026-11-13 9:13 ` kernel test robot
2026-11-13 17:35 ` Jamie Nguyen [this message]
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=20261113173522.1544082-1-jamien@nvidia.com \
--to=jamien@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=dmach@nvidia.com \
--cc=guohanjun@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lpieralisi@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