From: Vamsi Krishna <vattunuru@marvell.com>
To: <jerinj@marvell.com>
Cc: <dev@dpdk.org>, Vamsi Attunuru <vattunuru@marvell.com>,
<stable@dpdk.org>
Subject: [PATCH v0 1/1] net/octeon_ep: handle interrupt enable failure
Date: Mon, 14 Jul 2025 11:01:50 +0530 [thread overview]
Message-ID: <20250714053150.2229683-1-vattunuru@marvell.com> (raw)
From: Vamsi Attunuru <vattunuru@marvell.com>
Patch checks the return value of interrupt enable
and returns gracefully if file handler is not available.
Cc: stable@dpdk.org
Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
---
drivers/net/octeon_ep/otx_ep_mbox.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/net/octeon_ep/otx_ep_mbox.c b/drivers/net/octeon_ep/otx_ep_mbox.c
index 1d7e08d2cc..c83bb81474 100644
--- a/drivers/net/octeon_ep/otx_ep_mbox.c
+++ b/drivers/net/octeon_ep/otx_ep_mbox.c
@@ -355,16 +355,22 @@ otx_ep_mbox_init(struct rte_eth_dev *eth_dev)
struct otx_ep_device *otx_ep = (struct otx_ep_device *)eth_dev->data->dev_private;
struct rte_pci_device *pdev = RTE_ETH_DEV_TO_PCI(eth_dev);
uint64_t reg_val;
+ int rc;
otx_ep_mbox_version_check(otx_ep);
rte_intr_callback_register(pdev->intr_handle, otx_ep_mbox_intr_handler, (void *)eth_dev);
- if (rte_intr_enable(pdev->intr_handle)) {
+ rc = rte_intr_enable(pdev->intr_handle);
+
+ if (!(rc == -1 || rc == 0)) {
otx_ep_err("rte_intr_enable failed");
return -1;
}
+ if (rc == -1)
+ return 0;
+
reg_val = otx2_read64(otx_ep->hw_addr + CNXK_EP_R_MBOX_PF_VF_INT(0));
if (reg_val == UINT64_MAX)
return -ENODEV;
--
2.34.1
reply other threads:[~2025-07-14 5:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250714053150.2229683-1-vattunuru@marvell.com \
--to=vattunuru@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).