From: Steve Lin <steven.lin1@broadcom.com>
To: netdev@vger.kernel.org
Cc: jiri@mellanox.com, davem@davemloft.net,
michael.chan@broadcom.com, linux-pci@vger.kernel.org,
linville@tuxdriver.com, gospo@broadcom.com,
steven.lin1@broadcom.com
Subject: [RFC 0/3] Adding config get/set to devlink
Date: Thu, 12 Oct 2017 09:34:19 -0400 [thread overview]
Message-ID: <1507815262-33294-1-git-send-email-steven.lin1@broadcom.com> (raw)
Adds a devlink command for getting & setting device configuration
parameters, and enumerates a bunch of those parameters as devlink
attributes. Also introduces an attribute that can be set by a
driver to indicate that the config change doesn't take effect
until the next restart (as in the case of the bnxt driver changes
in this patchset, for which all the configuration changes affect NVM
only, and aren't loaded until the next restart.)
bnxt driver patches make use of these new devlink cmds/attributes.
Steve Lin (3):
devlink: Add config parameter get/set operations
bnxt: Move generic devlink code to new file
bnxt: Add devlink support for config get/set
drivers/net/ethernet/broadcom/bnxt/Makefile | 2 +-
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 1 +
drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c | 403 ++++++++++++++++++++++
drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.h | 56 +++
drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h | 100 ++++++
drivers/net/ethernet/broadcom/bnxt/bnxt_vfr.c | 97 +-----
drivers/net/ethernet/broadcom/bnxt/bnxt_vfr.h | 35 +-
include/net/devlink.h | 4 +
include/uapi/linux/devlink.h | 108 ++++++
net/core/devlink.c | 207 +++++++++++
10 files changed, 882 insertions(+), 131 deletions(-)
create mode 100644 drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c
create mode 100644 drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.h
--
2.7.4
next reply other threads:[~2017-10-12 13:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 13:34 Steve Lin [this message]
2017-10-12 13:34 ` [RFC 1/3] devlink: Add config parameter get/set operations Steve Lin
2017-10-12 14:03 ` Jiri Pirko
2017-10-12 14:37 ` Steve Lin
2017-10-12 18:12 ` Andy Gospodarek
2017-10-13 7:04 ` Jiri Pirko
2017-10-12 14:15 ` Jiri Pirko
2017-10-12 13:34 ` [RFC 2/3] bnxt: Move generic devlink code to new file Steve Lin
2017-10-12 13:34 ` [RFC 3/3] bnxt: Add devlink support for config get/set Steve Lin
2017-10-12 14:35 ` [RFC 0/3] Adding config get/set to devlink Roopa Prabhu
2017-10-12 14:40 ` Jiri Pirko
2017-10-12 14:46 ` Roopa Prabhu
2017-10-12 15:04 ` Jiri Pirko
2017-10-12 15:31 ` Roopa Prabhu
2017-10-12 15:43 ` Florian Fainelli
2017-10-12 16:05 ` Roopa Prabhu
2017-10-12 19:06 ` David Miller
2017-10-12 19:20 ` Florian Fainelli
2017-10-12 20:12 ` Steve Lin
2017-10-13 7:08 ` Jiri Pirko
2017-10-12 21:36 ` Michal Kubecek
2017-10-12 21:53 ` Roopa Prabhu
2017-10-13 7:11 ` Jiri Pirko
2017-10-14 4:21 ` Roopa Prabhu
2017-10-12 19:01 ` David Miller
2017-10-12 19:01 ` David Miller
2017-10-12 18:59 ` David Miller
2017-10-12 14:45 ` Steve Lin
2017-10-12 14:51 ` Roopa Prabhu
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=1507815262-33294-1-git-send-email-steven.lin1@broadcom.com \
--to=steven.lin1@broadcom.com \
--cc=davem@davemloft.net \
--cc=gospo@broadcom.com \
--cc=jiri@mellanox.com \
--cc=linux-pci@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
/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).