From: Subbaraya Sundeep <sbhatta@marvell.com>
To: <davem@davemloft.net>, <kuba@kernel.org>, <netdev@vger.kernel.org>
Cc: <hkelam@marvell.com>, <gakula@marvell.com>,
<sgoutham@marvell.com>, <rsaladi2@marvell.com>,
Subbaraya Sundeep <sbhatta@marvell.com>
Subject: [net-next PATCH 0/2] Add a devlink param and documentation
Date: Wed, 27 Oct 2021 16:01:13 +0530 [thread overview]
Message-ID: <1635330675-25592-1-git-send-email-sbhatta@marvell.com> (raw)
This patchset adds a new devlink parameter serdes_link
which is used in cases where physical link/SerDes needs to
be re-initialized. The existing interface up and down
sequence do not toggle SerDes configuration since PF and
all its VF share same physical link. Also documentation for
octeontx2 devlink parameters is missing hence documentation for
the implemented params is also added.
Patch 1 - Adds new serdes_link devlink parameter
Patch 2 - Adds documentation for all implemented devlink params
Thanks,
Sundeep
Rakesh Babu (1):
octeontx2-pf: Add devlink param to init and de-init serdes
Subbaraya Sundeep (1):
devlink: add documentation for octeontx2 driver
Documentation/networking/devlink/index.rst | 1 +
Documentation/networking/devlink/octeontx2.rst | 47 ++++++++++++++++++++++
drivers/net/ethernet/marvell/octeontx2/af/cgx.c | 11 +++++
drivers/net/ethernet/marvell/octeontx2/af/cgx.h | 1 +
drivers/net/ethernet/marvell/octeontx2/af/mbox.h | 7 ++++
.../net/ethernet/marvell/octeontx2/af/rvu_cgx.c | 24 +++++++++++
.../ethernet/marvell/octeontx2/nic/otx2_common.c | 20 +++++++++
.../ethernet/marvell/octeontx2/nic/otx2_common.h | 1 +
.../ethernet/marvell/octeontx2/nic/otx2_devlink.c | 29 +++++++++++++
9 files changed, 141 insertions(+)
create mode 100644 Documentation/networking/devlink/octeontx2.rst
--
2.7.4
next reply other threads:[~2021-10-27 10:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 10:31 Subbaraya Sundeep [this message]
2021-10-27 10:31 ` [net-next PATCH 1/2] octeontx2-pf: Add devlink param to init and de-init serdes Subbaraya Sundeep
2021-10-27 15:38 ` Jakub Kicinski
[not found] ` <PH0PR18MB4671C22DB7C8E5C46647860FA1859@PH0PR18MB4671.namprd18.prod.outlook.com>
2021-10-27 16:43 ` Fw: [EXT] " sundeep subbaraya
2021-10-27 17:08 ` Jakub Kicinski
2021-10-27 18:11 ` Ido Schimmel
[not found] ` <BY3PR18MB473794E01049EC94156E2858C6859@BY3PR18MB4737.namprd18.prod.outlook.com>
2021-10-27 22:24 ` Ido Schimmel
2021-10-28 12:18 ` sundeep subbaraya
2021-10-28 13:51 ` Ido Schimmel
2021-10-30 7:25 ` sundeep subbaraya
2021-11-07 9:21 ` Ido Schimmel
2021-11-08 15:54 ` Jakub Kicinski
2021-11-11 14:51 ` Ido Schimmel
2021-11-11 16:47 ` Jakub Kicinski
2021-11-14 8:38 ` Ido Schimmel
2021-11-15 4:19 ` Roopa Prabhu
2021-11-15 15:11 ` Jakub Kicinski
2021-11-19 10:47 ` sundeep subbaraya
2021-11-19 14:09 ` Jakub Kicinski
2021-11-19 14:26 ` sundeep subbaraya
2021-11-19 14:49 ` Jakub Kicinski
2021-10-27 10:31 ` [net-next PATCH 2/2] devlink: add documentation for octeontx2 driver Subbaraya Sundeep
2021-10-27 15:39 ` Jakub Kicinski
[not found] ` <PH0PR18MB46711B24C7305B8488266C8CA1859@PH0PR18MB4671.namprd18.prod.outlook.com>
2021-10-27 17:04 ` Fw: [EXT] " sundeep subbaraya
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=1635330675-25592-1-git-send-email-sbhatta@marvell.com \
--to=sbhatta@marvell.com \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rsaladi2@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).