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 0/2] firmware: xilinx: Feature check improvements
Date: Fri, 24 Jul 2026 02:53:50 -0700 [thread overview]
Message-ID: <20260724095352.2890326-1-jay.buddhabhatti@amd.com> (raw)
This series contains two independent improvements to the feature check
logic in the Xilinx firmware driver:
1. Use the TF-A dedicated PM_API_FEATURES mechanism to validate
TF-A-specific APIs instead of routing them through PM_FEATURE_CHECK.
Falls back to the legacy PM_FEATURE_CHECK for backward
compatibility.
2. When do_fw_call() fails in the feature check path, propagate the
actual errno from zynqmp_pm_ret_code() instead of always returning
-EOPNOTSUPP.
These were previously part of the kexec cleanup series
([PATCH 0/4] firmware: xilinx: Clean up firmware and TF-A state on kexec)
as patch 4/4 but are split out as they are general improvements independent
of the kexec functionality.
Jay Buddhabhatti (2):
firmware: xilinx: Use TF-A feature check for TF-A-specific APIs
firmware: xilinx: Propagate actual error from feature check
drivers/firmware/xilinx/zynqmp.c | 31 +++++++++++++++++--------------
1 file changed, 17 insertions(+), 14 deletions(-)
--
2.34.1
next 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 Jay Buddhabhatti [this message]
2026-07-24 9:53 ` [PATCH 1/2] firmware: xilinx: Use TF-A feature check for TF-A-specific APIs Jay Buddhabhatti
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-1-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®