From: Hariprasad Kelam <hkelam@marvell.com>
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <kuba@kernel.org>, <davem@davemloft.net>, <pabeni@redhat.com>,
<edumazet@google.com>, <sgoutham@marvell.com>,
<lcherian@marvell.com>, <gakula@marvell.com>,
<jerinj@marvell.com>, <sbhatta@marvell.com>
Subject: [net-next PATCH V2 0/4] CN10KB MAC block support
Date: Tue, 29 Nov 2022 10:44:05 +0530 [thread overview]
Message-ID: <20221129051409.20034-1-hkelam@marvell.com> (raw)
OcteonTx2's next gen platform the CN10KB has RPM_USX MAC which has a
different serdes when compared to RPM MAC. Though the underlying
HW is different, the CSR interface has been designed largely inline
with RPM MAC, with few exceptions though. So we are using the same
CGX driver for RPM_USX MAC as well and will have a different set of APIs
for RPM_USX where ever necessary.
The RPM and RPM_USX blocks support a different number of LMACS.
RPM_USX support 8 LMACS per MAC block whereas legacy RPM supports only 4
LMACS per MAC. with this RPM_USX support double the number of DMAC filters
and fifo size.
This patchset adds initial support for CN10KB's RPM_USX MAC i.e
registering the driver and defining MAC operations (mac_ops). With these
changes PF and VF netdev packet path will work and PF and VF netdev drivers
are able to configure MAC features like pause frames,PFC and loopback etc.
Also implements FEC stats for CN10K Mac block RPM and CN10KB Mac block
RPM_USX and extends ethtool support for PF and VF drivers by defining
get_fec_stats API to display FEC stats.
Hariprasad Kelam (3):
octeontx2-af: cn10kb: Add RPM_USX MAC support
octeontx2-pf: ethtool: Implement get_fec_stats
octeontx2-af: Add FEC stats for RPM/RPM_USX block
Rakesh Babu Saladi (1):
octeontx2-af: Support variable number of lmacs
.../net/ethernet/marvell/octeontx2/af/cgx.c | 78 ++++--
.../net/ethernet/marvell/octeontx2/af/cgx.h | 9 +-
.../marvell/octeontx2/af/lmac_common.h | 15 +-
.../net/ethernet/marvell/octeontx2/af/rpm.c | 262 ++++++++++++++++--
.../net/ethernet/marvell/octeontx2/af/rpm.h | 36 ++-
.../net/ethernet/marvell/octeontx2/af/rvu.h | 12 +-
.../ethernet/marvell/octeontx2/af/rvu_cgx.c | 49 +++-
.../marvell/octeontx2/af/rvu_debugfs.c | 2 +-
.../ethernet/marvell/octeontx2/af/rvu_nix.c | 10 +-
.../marvell/octeontx2/af/rvu_npc_hash.c | 4 +-
.../marvell/octeontx2/nic/otx2_ethtool.c | 75 ++---
11 files changed, 435 insertions(+), 117 deletions(-)
--
2.17.1
next reply other threads:[~2022-11-29 5:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 5:14 Hariprasad Kelam [this message]
2022-11-29 5:14 ` [net-next PATCH V2 1/4] octeontx2-af: Support variable number of lmacs Hariprasad Kelam
2022-11-29 5:14 ` [net-next PATCH V2 2/4] octeontx2-af: cn10kb: Add RPM_USX MAC support Hariprasad Kelam
2022-11-29 5:14 ` [net-next PATCH V2 3/4] octeontx2-pf: ethtool: Implement get_fec_stats Hariprasad Kelam
2022-11-29 18:45 ` Andrew Lunn
2022-11-30 8:54 ` Hariprasad Kelam
2022-11-29 5:14 ` [net-next PATCH V2 4/4] octeontx2-af: Add FEC stats for RPM/RPM_USX block Hariprasad Kelam
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=20221129051409.20034-1-hkelam@marvell.com \
--to=hkelam@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®