From: Moshe Shemesh <moshe@mellanox.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: Alexander Duyck <alexander.duyck@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Moshe Shemesh <moshe@mellanox.com>
Subject: [PATCH net-next RFC 0/3] Add mlx5 devices FW upgrade reset support
Date: Tue, 14 Jan 2020 17:55:25 +0200 [thread overview]
Message-ID: <1579017328-19643-1-git-send-email-moshe@mellanox.com> (raw)
This patchset adds support for FW upgrade.
On devlink reload, if a pending FW image is found, the driver will perform
a FW upgrade reset flow to activate the pending FW image.
Sending as RFC because the FW activation reset requires a pci link
toggling. Although it works and we verify that the device is the only
device on the pcie bridge before allowing such reset, as already done by
other drivers [1], we would like to get some feedback on the last patch
of this series.
[1] function trigger_sbr() at drivers/infiniband/hw/hfi1/pcie.c
Moshe Shemesh (3):
net/mlx5: Add structure layout and defines for MFRL register
net/mlx5: Add functions to set/query MFRL register
net/mlx5: Add FW upgrade reset support
drivers/net/ethernet/mellanox/mlx5/core/devlink.c | 81 +++++++++++++++++++++-
drivers/net/ethernet/mellanox/mlx5/core/fw.c | 44 ++++++++++++
.../net/ethernet/mellanox/mlx5/core/mlx5_core.h | 2 +
include/linux/mlx5/driver.h | 1 +
include/linux/mlx5/mlx5_ifc.h | 17 +++++
5 files changed, 144 insertions(+), 1 deletion(-)
--
1.8.3.1
next reply other threads:[~2020-01-14 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 15:55 Moshe Shemesh [this message]
2020-01-14 15:55 ` [PATCH net-next RFC 1/3] net/mlx5: Add structure layout and defines for MFRL register Moshe Shemesh
2020-01-14 15:55 ` [PATCH net-next RFC 2/3] net/mlx5: Add functions to set/query " Moshe Shemesh
2020-01-14 15:55 ` [PATCH net-next RFC 3/3] net/mlx5: Add FW upgrade reset support Moshe Shemesh
2020-01-15 15:01 ` Jakub Kicinski
2020-01-16 14:52 ` Moshe Shemesh
2020-01-17 1:26 ` Jakub Kicinski
2020-01-18 19:57 ` Moshe Shemesh
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=1579017328-19643-1-git-send-email-moshe@mellanox.com \
--to=moshe@mellanox.com \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.