From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: andrew@lunn.ch, vivien.didelot@gmail.com, f.fainelli@gmail.com,
kuba@kernel.org, cphealy@gmail.com, jiri@nvidia.com
Subject: [PATCH v2 net-next 0/3] Devlink regions for SJA1105 DSA driver
Date: Sat, 26 Sep 2020 02:04:18 +0300 [thread overview]
Message-ID: <20200925230421.711991-1-vladimir.oltean@nxp.com> (raw)
This series exposes the SJA1105 static config as a devlink region. This
can be used for debugging, for example with the sja1105_dump user space
program that I have derived from Andrew Lunn's mv88e6xxx_dump:
https://github.com/vladimiroltean/mv88e6xxx_dump/tree/sja1105
Changes in v2:
- Tear down devlink params on initialization failure.
- Add driver identification through devlink.
Vladimir Oltean (3):
net: dsa: sja1105: move devlink param code to sja1105_devlink.c
net: dsa: sja1105: expose static config as devlink region
net: dsa: sja1105: implement .devlink_info_get
drivers/net/dsa/sja1105/Makefile | 1 +
drivers/net/dsa/sja1105/sja1105.h | 16 +-
drivers/net/dsa/sja1105/sja1105_devlink.c | 255 ++++++++++++++++++++++
drivers/net/dsa/sja1105/sja1105_main.c | 106 +--------
drivers/net/dsa/sja1105/sja1105_spi.c | 5 +-
5 files changed, 277 insertions(+), 106 deletions(-)
create mode 100644 drivers/net/dsa/sja1105/sja1105_devlink.c
--
2.25.1
next reply other threads:[~2020-09-25 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 23:04 Vladimir Oltean [this message]
2020-09-25 23:04 ` [PATCH v2 net-next 1/3] net: dsa: sja1105: move devlink param code to sja1105_devlink.c Vladimir Oltean
2020-09-25 23:04 ` [PATCH v2 net-next 2/3] net: dsa: sja1105: expose static config as devlink region Vladimir Oltean
2020-09-25 23:04 ` [PATCH v2 net-next 3/3] net: dsa: sja1105: implement .devlink_info_get Vladimir Oltean
2020-09-25 23:35 ` [PATCH v2 net-next 0/3] Devlink regions for SJA1105 DSA driver David Miller
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=20200925230421.711991-1-vladimir.oltean@nxp.com \
--to=vladimir.oltean@nxp.com \
--cc=andrew@lunn.ch \
--cc=cphealy@gmail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@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).