From: Michael Chan <michael.chan@broadcom.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, kuba@kernel.org, gospo@broadcom.com
Subject: [PATCH net-next 00/11] bnxt_en: net-next updates.
Date: Sun, 4 Oct 2020 15:22:50 -0400 [thread overview]
Message-ID: <1601839381-10446-1-git-send-email-michael.chan@broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
This series starts off with the usual update of the firmware interface
spec. A new firmware status bit in the interface will be used in patch
#4 to perform recovery on some SoC platforms. Patches #2 and #3 first
add the infrastructure to read the firmware status very early during
driver probe and this will allow patch #4 to do the recovery if needed.
The rest of the patches add improvements to the current RX reset
logic by localizing the reset to the affected RX ring only and to
reset only if firmware has determined that the RX ring is in permanent
error state.
EdwinePeer (3):
bnxt_en: refactor bnxt_alloc_fw_health()
bnxt_en: log firmware status on firmware init failure
bnxt_en: perform no master recovery during startup
Michael Chan (7):
bnxt_en: Log FW health status info, if reset is aborted.
bnxt_en: Refactor bnxt_free_rx_skbs().
bnxt_en: Refactor bnxt_init_one_rx_ring().
bnxt_en: Implement RX ring reset in response to buffer errors.
bnxt_en: Add a software counter for RX ring reset.
bnxt_en: Reduce unnecessary message log during RX errors.
bnxt_en: Eliminate unnecessary RX resets.
Vasundhara Volam (1):
bnxt_en: Update firmware interface spec to 1.10.1.68.
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 529 +++++++++++++-----
drivers/net/ethernet/broadcom/bnxt/bnxt.h | 6 +
.../net/ethernet/broadcom/bnxt/bnxt_ethtool.c | 1 +
drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h | 24 +-
4 files changed, 403 insertions(+), 157 deletions(-)
--
2.18.1
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4166 bytes --]
next reply other threads:[~2020-10-04 19:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 19:22 Michael Chan [this message]
2020-10-04 19:22 ` [PATCH net-next 01/11] bnxt_en: Update firmware interface spec to 1.10.1.68 Michael Chan
2020-10-04 19:22 ` [PATCH net-next 02/11] bnxt_en: refactor bnxt_alloc_fw_health() Michael Chan
2020-10-04 19:22 ` [PATCH net-next 03/11] bnxt_en: log firmware status on firmware init failure Michael Chan
2020-10-04 19:22 ` [PATCH net-next 04/11] bnxt_en: perform no master recovery during startup Michael Chan
2020-10-04 19:22 ` [PATCH net-next 05/11] bnxt_en: Log FW health status info, if reset is aborted Michael Chan
2020-10-04 19:22 ` [PATCH net-next 06/11] bnxt_en: Refactor bnxt_free_rx_skbs() Michael Chan
2020-10-04 19:22 ` [PATCH net-next 07/11] bnxt_en: Refactor bnxt_init_one_rx_ring() Michael Chan
2020-10-04 19:22 ` [PATCH net-next 08/11] bnxt_en: Implement RX ring reset in response to buffer errors Michael Chan
2020-10-04 19:22 ` [PATCH net-next 09/11] bnxt_en: Add a software counter for RX ring reset Michael Chan
2020-10-04 19:23 ` [PATCH net-next 10/11] bnxt_en: Reduce unnecessary message log during RX errors Michael Chan
2020-10-04 19:23 ` [PATCH net-next 11/11] bnxt_en: Eliminate unnecessary RX resets Michael Chan
2020-10-04 21:41 ` [PATCH net-next 00/11] bnxt_en: net-next updates 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=1601839381-10446-1-git-send-email-michael.chan@broadcom.com \
--to=michael.chan@broadcom.com \
--cc=davem@davemloft.net \
--cc=gospo@broadcom.com \
--cc=kuba@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 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).