From: Srujana Challa <schalla@marvell.com>
To: <netdev@vger.kernel.org>
Cc: <davem@davemloft.net>, <kuba@kernel.org>, <edumazet@google.com>,
<pabeni@redhat.com>, <jerinj@marvell.com>, <sgoutham@marvell.com>,
<lcherian@marvell.com>, <gakula@marvell.com>,
<sbhatta@marvell.com>, <hkelam@marvell.com>,
<schalla@marvell.com>
Subject: [PATCH v1 net-next,0/8] octeontx2-af: Miscellaneous changes for CPT
Date: Tue, 10 Jan 2023 11:52:50 +0530 [thread overview]
Message-ID: <20230110062258.892887-1-schalla@marvell.com> (raw)
This patchset consists of miscellaneous changes for CPT.
- Adds a new mailbox to reset the requested CPT LF.
- Modify FLR sequence as per HW team suggested.
- Adds support to recover CPT engines when they gets fault.
- Updates CPT inbound inline IPsec configuration mailbox,
as per new generation of the OcteonTX2 chips.
- Adds a new mailbox to retuen CPT FLT Interrupt info.
---
v1:
- Dropped patch "octeontx2-af: Fix interrupt name strings completely"
to submit to net.
---
Nithin Dabilpuram (1):
octeontx2-af: restore rxc conf after teardown sequence
Srujana Challa (7):
octeontx2-af: recover CPT engine when it gets fault
octeontx2-af: add mbox for CPT LF reset
octeontx2-af: modify FLR sequence for CPT
octeontx2-af: optimize cpt pf identification
octeontx2-af: update CPT inbound inline IPsec config mailbox
octeontx2-af: add ctx ilen to cpt lf alloc mailbox
octeontx2-af: add mbox to return CPT_AF_FLT_INT info
.../net/ethernet/marvell/octeontx2/af/mbox.h | 33 +-
.../net/ethernet/marvell/octeontx2/af/rvu.c | 8 +
.../net/ethernet/marvell/octeontx2/af/rvu.h | 18 ++
.../ethernet/marvell/octeontx2/af/rvu_cpt.c | 305 +++++++++++++-----
.../ethernet/marvell/octeontx2/af/rvu_nix.c | 46 ++-
.../ethernet/marvell/octeontx2/af/rvu_reg.h | 2 +
6 files changed, 322 insertions(+), 90 deletions(-)
--
2.25.1
next reply other threads:[~2023-01-10 6:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 6:22 Srujana Challa [this message]
2023-01-10 6:22 ` [PATCH v1 net-next,1/8] octeontx2-af: recover CPT engine when it gets fault Srujana Challa
2023-01-10 6:22 ` [PATCH v1 net-next,2/8] octeontx2-af: add mbox for CPT LF reset Srujana Challa
2023-01-10 6:22 ` [PATCH v1 net-next,3/8] octeontx2-af: modify FLR sequence for CPT Srujana Challa
2023-01-10 6:22 ` [PATCH v1 net-next,4/8] octeontx2-af: optimize cpt pf identification Srujana Challa
2023-01-10 6:22 ` [PATCH v1 net-next,5/8] octeontx2-af: restore rxc conf after teardown sequence Srujana Challa
2023-01-10 6:22 ` [PATCH v1 net-next,6/8] octeontx2-af: update CPT inbound inline IPsec config mailbox Srujana Challa
2023-01-10 6:22 ` [PATCH v1 net-next,7/8] octeontx2-af: add ctx ilen to cpt lf alloc mailbox Srujana Challa
2023-01-10 6:22 ` [PATCH v1 net-next,8/8] octeontx2-af: add mbox to return CPT_AF_FLT_INT info Srujana Challa
2023-01-10 12:11 ` Leon Romanovsky
2023-01-11 11:20 ` [EXT] " Srujana Challa
-- strict thread matches above, loose matches on Subject: below --
2023-01-10 6:20 [PATCH v1 net-next,0/8] octeontx2-af: Miscellaneous changes for CPT Srujana Challa
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=20230110062258.892887-1-schalla@marvell.com \
--to=schalla@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@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;
as well as URLs for NNTP newsgroup(s).