From: Jay Buddhabhatti <jay.buddhabhatti@amd.com>
To: <michal.simek@amd.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <ptsm@linux.microsoft.com>,
<radhey.shyam.pandey@amd.com>,
Jay Buddhabhatti <jay.buddhabhatti@amd.com>
Subject: [PATCH 1/2] firmware: xilinx: Use TF-A feature check for TF-A-specific APIs
Date: Fri, 24 Jul 2026 02:53:51 -0700 [thread overview]
Message-ID: <20260724095352.2890326-2-jay.buddhabhatti@amd.com> (raw)
In-Reply-To: <20260724095352.2890326-1-jay.buddhabhatti@amd.com>
Currently, TF-A-specific APIs are validated using the firmware
PM_FEATURE_CHECK API, even though TF-A provides a dedicated mechanism
via PM_API_FEATURES API. Update the feature check logic for TF-A-specific
API calls to use PM_API_FEATURES. If this check fails, fall back to the
legacy PM_FEATURE_CHECK to support backward compatibility.
Signed-off-by: Jay Buddhabhatti <jay.buddhabhatti@amd.com>
Reviewed-by: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
Reviewed-by: Prasanna Kumar T S M <ptsm@linux.microsoft.com>
---
drivers/firmware/xilinx/zynqmp.c | 25 +++++++++++++++----------
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git a/drivers/firmware/xilinx/zynqmp.c b/drivers/firmware/xilinx/zynqmp.c
index fc7212f554ee..95f5941c5ca8 100644
--- a/drivers/firmware/xilinx/zynqmp.c
+++ b/drivers/firmware/xilinx/zynqmp.c
@@ -224,28 +224,33 @@ static int __do_feature_check_call(const u32 api_id, u32 *ret_payload)
module_id = FIELD_GET(MODULE_ID_MASK, api_id);
/*
- * Feature check of APIs belonging to PM, XSEM, and TF-A are handled by calling
+ * Feature check of APIs belonging to PM and XSEM are handled by calling
* PM_FEATURE_CHECK API. For other modules, call PM_API_FEATURES API.
*/
- if (module_id == PM_MODULE_ID || module_id == XSEM_MODULE_ID || module_id == TF_A_MODULE_ID)
+ if (module_id == PM_MODULE_ID || module_id == XSEM_MODULE_ID)
feature_check_api_id = PM_FEATURE_CHECK;
else
feature_check_api_id = PM_API_FEATURES;
- /*
- * Feature check of TF-A APIs is done in the TF-A layer and it expects for
- * MODULE_ID_MASK bits of SMC's arg[0] to be the same as PM_MODULE_ID.
- */
- if (module_id == TF_A_MODULE_ID) {
- module_id = PM_MODULE_ID;
+ if (module_id == TF_A_MODULE_ID)
smc_arg[1] = api_id;
- } else {
+ else
smc_arg[1] = (api_id & API_ID_MASK);
- }
smc_arg[0] = PM_SIP_SVC | FIELD_PREP(MODULE_ID_MASK, module_id) | feature_check_api_id;
ret = do_fw_call(ret_payload, 2, smc_arg[0], smc_arg[1]);
+
+ /*
+ * For TF-A APIs, if the feature check with PM_API_FEATURES fails,
+ * retry with the legacy PM_FEATURE_CHECK for backward compatibility.
+ */
+ if (module_id == TF_A_MODULE_ID && ret) {
+ smc_arg[0] = PM_SIP_SVC | FIELD_PREP(MODULE_ID_MASK, PM_MODULE_ID) |
+ PM_FEATURE_CHECK;
+ ret = do_fw_call(ret_payload, 2, smc_arg[0], smc_arg[1]);
+ }
+
if (ret)
ret = -EOPNOTSUPP;
else
--
2.34.1
next prev parent reply other threads:[~2026-07-24 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 9:53 [PATCH 0/2] firmware: xilinx: Feature check improvements Jay Buddhabhatti
2026-07-24 9:53 ` Jay Buddhabhatti [this message]
2026-07-24 9:53 ` [PATCH 2/2] firmware: xilinx: Propagate actual error from feature check Jay Buddhabhatti
2026-08-06 13:18 ` [PATCH 0/2] firmware: xilinx: Feature check improvements Michal Simek
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=20260724095352.2890326-2-jay.buddhabhatti@amd.com \
--to=jay.buddhabhatti@amd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=ptsm@linux.microsoft.com \
--cc=radhey.shyam.pandey@amd.com \
/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®