From: Michael Chan <michael.chan@broadcom.com>
To: davem@davemloft.net, jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org
Subject: [PATCH net-next v2 00/13] bnxt_en: Updates.
Date: Sat, 23 Nov 2019 22:30:37 -0500 [thread overview]
Message-ID: <1574566250-7546-1-git-send-email-michael.chan@broadcom.com> (raw)
v2: Dropped the devlink info patches to address some feedback and resubmit for
the 5.6 kernel.
This patchset contains these main features:
1. Add the proper logic to support suspend/resume on the new 57500 chips.
2. Allow Phy configurations from user on a Multihost function if supported
by fw.
3. devlink NVRAM flashing support.
4. Add a couple of chip IDs, PHY loopback enhancement, and provide more RSS
contexts to VFs.
Michael Chan (8):
bnxt_en: Add chip IDs for 57452 and 57454 chips.
bnxt_en: Disable/enable Bus master during suspend/resume.
bnxt_en: Initialize context memory to the value specified by firmware.
bnxt_en: Assign more RSS context resources to the VFs.
bnxt_en: Skip disabling autoneg before PHY loopback when appropriate.
bnxt_en: Refactor the initialization of the ethtool link settings.
bnxt_en: Add async. event logic for PHY configuration changes.
bnxt_en: Allow PHY settings on multi-function or NPAR PFs if allowed
by FW.
Vasundhara Volam (5):
bnxt_en: Do driver unregister cleanup in bnxt_init_one() failure path.
bnxt_en: Combine 2 functions calling the same HWRM_DRV_RGTR fw
command.
bnxt_en: Send FUNC_RESOURCE_QCAPS command in bnxt_resume()
bnxt_en: Fix suspend/resume path on 57500 chips
bnxt_en: Add support for flashing the device via devlink
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 212 ++++++++++++++--------
drivers/net/ethernet/broadcom/bnxt/bnxt.h | 21 ++-
drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c | 20 ++
drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.c | 15 +-
drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.h | 2 +
drivers/net/ethernet/broadcom/bnxt/bnxt_sriov.c | 8 +-
drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c | 4 +-
7 files changed, 190 insertions(+), 92 deletions(-)
--
2.5.1
next reply other threads:[~2019-11-24 3:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-24 3:30 Michael Chan [this message]
2019-11-24 3:30 ` [PATCH net-next v2 01/13] bnxt_en: Add chip IDs for 57452 and 57454 chips Michael Chan
2019-11-24 3:30 ` [PATCH net-next v2 02/13] bnxt_en: Disable/enable Bus master during suspend/resume Michael Chan
2019-11-24 3:30 ` [PATCH net-next v2 03/13] bnxt_en: Do driver unregister cleanup in bnxt_init_one() failure path Michael Chan
2019-11-24 3:30 ` [PATCH net-next v2 04/13] bnxt_en: Combine 2 functions calling the same HWRM_DRV_RGTR fw command Michael Chan
2019-11-24 3:30 ` [PATCH net-next v2 05/13] bnxt_en: Send FUNC_RESOURCE_QCAPS command in bnxt_resume() Michael Chan
2019-11-24 3:30 ` [PATCH net-next v2 06/13] bnxt_en: Fix suspend/resume path on 57500 chips Michael Chan
2019-11-24 3:30 ` [PATCH net-next v2 07/13] bnxt_en: Initialize context memory to the value specified by firmware Michael Chan
2019-11-24 3:30 ` [PATCH net-next v2 08/13] bnxt_en: Assign more RSS context resources to the VFs Michael Chan
2019-11-24 3:30 ` [PATCH net-next v2 09/13] bnxt_en: Skip disabling autoneg before PHY loopback when appropriate Michael Chan
2019-11-24 3:30 ` [PATCH net-next v2 10/13] bnxt_en: Refactor the initialization of the ethtool link settings Michael Chan
2019-11-24 3:30 ` [PATCH net-next v2 11/13] bnxt_en: Add async. event logic for PHY configuration changes Michael Chan
2019-11-24 3:30 ` [PATCH net-next v2 12/13] bnxt_en: Allow PHY settings on multi-function or NPAR PFs if allowed by FW Michael Chan
2019-11-24 3:30 ` [PATCH net-next v2 13/13] bnxt_en: Add support for flashing the device via devlink Michael Chan
2019-11-25 10:19 ` Jiri Pirko
2019-11-26 3:52 ` Vasundhara Volam
2019-11-24 22:55 ` [PATCH net-next v2 00/13] bnxt_en: Updates Jakub Kicinski
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=1574566250-7546-1-git-send-email-michael.chan@broadcom.com \
--to=michael.chan@broadcom.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.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).