From: Hariprasad Kelam <hkelam@marvell.com>
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <kuba@kernel.org>, <davem@davemloft.net>,
<willemdebruijn.kernel@gmail.com>, <andrew@lunn.ch>,
<sgoutham@marvell.com>, <lcherian@marvell.com>,
<gakula@marvell.com>, <jerinj@marvell.com>, <sbhatta@marvell.com>,
<hkelam@marvell.com>
Subject: [Patch v3 net-next 0/7] ethtool support for fec and link configuration
Date: Mon, 1 Feb 2021 10:54:37 +0530 [thread overview]
Message-ID: <1612157084-101715-1-git-send-email-hkelam@marvell.com> (raw)
This series of patches add support for forward error correction(fec) and
physical link configuration. Patches 1&2 adds necessary mbox handlers for fec
mode configuration request and to fetch stats. Patch 3 registers driver
callbacks for fec mode configuration and display. Patch 4&5 adds support of mbox
handlers for configuring link parameters like speed/duplex and autoneg etc.
Patche 6&7 registers driver callbacks for physical link configuration.
Change-log:
v2:
- Fixed review comments
- Corrected indentation issues
- Return -ENOMEM incase of mbox allocation failure
- added validation for input fecparams bitmask values
- added more comments
V3:
- Removed inline functions
- Make use of ethtool helpers APIs to display supported
advertised modes
- corrected indentation issues
- code changes such that return early in case of failure
to aid branch prediction
Christina Jacob (6):
octeontx2-af: forward error correction configuration
octeontx2-pf: ethtool fec mode support
octeontx2-af: Physical link configuration support
octeontx2-af: advertised link modes support on cgx
octeontx2-pf: ethtool physical link status
octeontx2-pf: ethtool physical link configuration
Felix Manlunas (1):
octeontx2-af: Add new CGX_CMD to get PHY FEC statistics
drivers/net/ethernet/marvell/octeontx2/af/cgx.c | 258 ++++++++++++-
drivers/net/ethernet/marvell/octeontx2/af/cgx.h | 10 +
.../net/ethernet/marvell/octeontx2/af/cgx_fw_if.h | 70 +++-
drivers/net/ethernet/marvell/octeontx2/af/mbox.h | 87 ++++-
drivers/net/ethernet/marvell/octeontx2/af/rvu.h | 4 +
.../net/ethernet/marvell/octeontx2/af/rvu_cgx.c | 80 +++++
.../ethernet/marvell/octeontx2/nic/otx2_common.c | 20 ++
.../ethernet/marvell/octeontx2/nic/otx2_common.h | 6 +
.../ethernet/marvell/octeontx2/nic/otx2_ethtool.c | 399 ++++++++++++++++++++-
.../net/ethernet/marvell/octeontx2/nic/otx2_pf.c | 3 +
10 files changed, 930 insertions(+), 7 deletions(-)
--
2.7.4
next reply other threads:[~2021-02-01 6:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 5:24 Hariprasad Kelam [this message]
2021-02-01 5:24 ` [Patch v3 net-next 1/7] octeontx2-af: forward error correction configuration Hariprasad Kelam
2021-02-03 0:43 ` Jesse Brandeburg
2021-02-01 5:24 ` [Patch v3 net-next 2/7] octeontx2-af: Add new CGX_CMD to get PHY FEC statistics Hariprasad Kelam
2021-02-03 0:43 ` Jesse Brandeburg
2021-02-01 5:24 ` [Patch v3 net-next 3/7] octeontx2-pf: ethtool fec mode support Hariprasad Kelam
2021-02-03 0:44 ` Jesse Brandeburg
2021-02-03 1:12 ` Jakub Kicinski
2021-02-01 5:24 ` [Patch v3 net-next 4/7] octeontx2-af: Physical link configuration support Hariprasad Kelam
2021-02-03 0:44 ` Jesse Brandeburg
2021-02-01 5:24 ` [Patch v3 net-next 5/7] octeontx2-af: advertised link modes support on cgx Hariprasad Kelam
2021-02-03 0:45 ` Jesse Brandeburg
2022-12-01 2:02 ` Chris Packham
2022-12-02 7:56 ` Hariprasad Kelam
2021-02-01 5:24 ` [Patch v3 net-next 6/7] octeontx2-pf: ethtool physical link status Hariprasad Kelam
2021-02-03 0:46 ` Jesse Brandeburg
2021-02-01 5:24 ` [Patch v3 net-next 7/7] octeontx2-pf: ethtool physical link configuration Hariprasad Kelam
2021-02-03 0:48 ` Jesse Brandeburg
2021-02-03 0:41 ` [Patch v3 net-next 0/7] ethtool support for fec and " Jesse Brandeburg
[not found] <1612098665-187767-1-git-send-email-hkelam@marvell.com>
2021-02-01 0:54 ` Willem de Bruijn
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=1612157084-101715-1-git-send-email-hkelam@marvell.com \
--to=hkelam@marvell.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--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=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=willemdebruijn.kernel@gmail.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).