From: Vimlesh Kumar <vimleshk@marvell.com>
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <sedara@marvell.com>, <srasheed@marvell.com>, <hgani@marvell.com>,
"Vimlesh Kumar" <vimleshk@marvell.com>
Subject: [PATCH net v3 0/3] disable interrupts and ensure dbell updation
Date: Wed, 7 Jan 2026 13:18:53 +0000 [thread overview]
Message-ID: <20260107131857.3434352-1-vimleshk@marvell.com> (raw)
Disable per ring interrupts when netdev goes down and ensure dbell BADDR
updation for both PFs and VFs by adding wait and check for updated value.
Vimlesh Kumar (3):
octeon_ep: disable per ring interrupts
octeon_ep: ensure dbell BADDR updation
octeon_ep_vf: ensure dbell BADDR updation
V3:
- Use reverse christmas tree order variable declaration.
- Return error if timeout happens during setup oq.
V2: https://lore.kernel.org/all/20251219100751.3063135-1-vimleshk@marvell.com/
V1: https://lore.kernel.org/all/20251212122304.2562229-1-vimleshk@marvell.com/
.../marvell/octeon_ep/octep_cn9k_pf.c | 21 ++++--
.../marvell/octeon_ep/octep_cnxk_pf.c | 64 +++++++++++++++----
.../ethernet/marvell/octeon_ep/octep_main.h | 2 +-
.../marvell/octeon_ep/octep_regs_cn9k_pf.h | 1 +
.../marvell/octeon_ep/octep_regs_cnxk_pf.h | 1 +
.../net/ethernet/marvell/octeon_ep/octep_rx.c | 4 +-
.../marvell/octeon_ep_vf/octep_vf_cn9k.c | 3 +-
.../marvell/octeon_ep_vf/octep_vf_cnxk.c | 39 ++++++++++-
.../marvell/octeon_ep_vf/octep_vf_main.h | 2 +-
.../marvell/octeon_ep_vf/octep_vf_rx.c | 4 +-
10 files changed, 118 insertions(+), 23 deletions(-)
--
2.47.0
next reply other threads:[~2026-01-07 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 13:18 Vimlesh Kumar [this message]
2026-01-07 13:18 ` [PATCH net v3 1/3] octeon_ep: disable per ring interrupts Vimlesh Kumar
2026-01-07 13:18 ` [PATCH net v3 2/3] octeon_ep: ensure dbell BADDR updation Vimlesh Kumar
2026-01-07 13:18 ` [PATCH net v3 3/3] octeon_ep_vf: " Vimlesh Kumar
2026-01-12 14:39 ` Simon Horman
2026-01-15 9:34 ` [EXTERNAL] " Vimlesh Kumar
2026-01-15 13:46 ` Simon Horman
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=20260107131857.3434352-1-vimleshk@marvell.com \
--to=vimleshk@marvell.com \
--cc=hgani@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sedara@marvell.com \
--cc=srasheed@marvell.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