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 2/2] firmware: xilinx: Propagate actual error from feature check
Date: Fri, 24 Jul 2026 02:53:52 -0700 [thread overview]
Message-ID: <20260724095352.2890326-3-jay.buddhabhatti@amd.com> (raw)
In-Reply-To: <20260724095352.2890326-1-jay.buddhabhatti@amd.com>
When do_fw_call() fails in __do_feature_check_call(), propagate the
actual errno from zynqmp_pm_ret_code() instead of always returning
-EOPNOTSUPP. This gives callers more precise error information. Existing
callers only test ret < 0 and are unchanged by this.
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 | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/firmware/xilinx/zynqmp.c b/drivers/firmware/xilinx/zynqmp.c
index 95f5941c5ca8..0b6c20a1d8be 100644
--- a/drivers/firmware/xilinx/zynqmp.c
+++ b/drivers/firmware/xilinx/zynqmp.c
@@ -252,11 +252,9 @@ static int __do_feature_check_call(const u32 api_id, u32 *ret_payload)
}
if (ret)
- ret = -EOPNOTSUPP;
- else
- ret = ret_payload[1];
+ return ret;
- return ret;
+ return ret_payload[1];
}
static int do_feature_check_call(const u32 api_id)
--
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 ` [PATCH 1/2] firmware: xilinx: Use TF-A feature check for TF-A-specific APIs Jay Buddhabhatti
2026-07-24 9:53 ` Jay Buddhabhatti [this message]
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-3-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®