From: Vikas Gupta <vikas.gupta@broadcom.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
vsrama-krishna.nemani@broadcom.com,
Vikas Gupta <vikas.gupta@broadcom.com>
Subject: [net-next, 00/10] Introducing Broadcom BNGE Ethernet Driver
Date: Wed, 18 Jun 2025 14:47:30 +0000 [thread overview]
Message-ID: <20250618144743.843815-1-vikas.gupta@broadcom.com> (raw)
Hi,
This patch series introduces the Ethernet driver for Broadcom’s
BCM5770X chip family, which supports 50/100/200/400/800 Gbps
link speeds. The driver is built as the bng_en.ko kernel module.
To keep the series within a reviewable size (~5K lines of code), this initial
submission focuses on the core infrastructure and initialization, including:
1) PCIe support (device IDs, probe/remove)
2) Devlink support
3) Firmware communication mechanism
4) Creation of network device
5) PF Resource management (rings, IRQs, etc. for netdev & aux dev)
Support for Tx/Rx datapaths, link management, ethtool/devlink operations and
additional features will be introduced in the subsequent patch series.
The bng_en driver shares the bnxt_hsi.h file with the bnxt_en driver, as the bng_en
driver leverages the hardware communication protocol used by the bnxt_en driver.
Thanks,
Vikas
Vikas Gupta (10):
bng_en: Add PCI interface
bng_en: Add devlink interface
bng_en: Add firmware communication mechanism
bng_en: Add initial interaction with firmware
bng_en: Add ring memory allocation support
bng_en: Add backing store support
bng_en: Add resource management support
bng_en: Add irq allocation support
bng_en: Initialize default configuration
bng_en: Add a network device
MAINTAINERS | 6 +
drivers/net/ethernet/broadcom/Kconfig | 9 +
drivers/net/ethernet/broadcom/Makefile | 1 +
drivers/net/ethernet/broadcom/bnge/Makefile | 12 +
drivers/net/ethernet/broadcom/bnge/bnge.h | 218 ++++++
.../net/ethernet/broadcom/bnge/bnge_core.c | 395 ++++++++++
.../net/ethernet/broadcom/bnge/bnge_devlink.c | 267 +++++++
.../net/ethernet/broadcom/bnge/bnge_devlink.h | 18 +
.../net/ethernet/broadcom/bnge/bnge_ethtool.c | 33 +
.../net/ethernet/broadcom/bnge/bnge_ethtool.h | 9 +
.../net/ethernet/broadcom/bnge/bnge_hwrm.c | 503 +++++++++++++
.../net/ethernet/broadcom/bnge/bnge_hwrm.h | 117 +++
.../ethernet/broadcom/bnge/bnge_hwrm_lib.c | 703 ++++++++++++++++++
.../ethernet/broadcom/bnge/bnge_hwrm_lib.h | 27 +
.../net/ethernet/broadcom/bnge/bnge_netdev.c | 266 +++++++
.../net/ethernet/broadcom/bnge/bnge_netdev.h | 206 +++++
.../net/ethernet/broadcom/bnge/bnge_resc.c | 604 +++++++++++++++
.../net/ethernet/broadcom/bnge/bnge_resc.h | 94 +++
.../net/ethernet/broadcom/bnge/bnge_rmem.c | 438 +++++++++++
.../net/ethernet/broadcom/bnge/bnge_rmem.h | 188 +++++
20 files changed, 4114 insertions(+)
create mode 100644 drivers/net/ethernet/broadcom/bnge/Makefile
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge.h
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_core.c
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_devlink.c
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_devlink.h
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_ethtool.c
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_ethtool.h
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_hwrm.c
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_hwrm.h
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_hwrm_lib.c
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_hwrm_lib.h
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_netdev.c
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_netdev.h
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_resc.c
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_resc.h
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_rmem.c
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_rmem.h
--
2.47.1
next reply other threads:[~2025-06-18 9:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 14:47 Vikas Gupta [this message]
2025-06-18 14:47 ` [net-next, 01/10] bng_en: Add PCI interface Vikas Gupta
2025-06-19 12:25 ` Vadim Fedorenko
2025-06-18 14:47 ` [net-next, 02/10] bng_en: Add devlink interface Vikas Gupta
2025-06-19 12:34 ` Vadim Fedorenko
2025-06-18 14:47 ` [net-next, 03/10] bng_en: Add firmware communication mechanism Vikas Gupta
2025-06-19 9:46 ` kernel test robot
2025-06-19 12:43 ` Vadim Fedorenko
2025-06-24 10:23 ` Vikas Gupta
2025-06-18 14:47 ` [net-next, 04/10] bng_en: Add initial interaction with firmware Vikas Gupta
2025-06-19 12:53 ` Vadim Fedorenko
2025-06-24 10:26 ` Vikas Gupta
2025-06-24 12:11 ` Vadim Fedorenko
2025-06-25 9:29 ` Vikas Gupta
2025-06-25 10:24 ` Vadim Fedorenko
2025-06-18 14:47 ` [net-next, 05/10] bng_en: Add ring memory allocation support Vikas Gupta
2025-06-18 14:47 ` [net-next, 06/10] bng_en: Add backing store support Vikas Gupta
2025-06-19 13:02 ` Vadim Fedorenko
2025-06-24 10:29 ` Vikas Gupta
2025-06-24 12:12 ` Vadim Fedorenko
2025-06-18 14:47 ` [net-next, 07/10] bng_en: Add resource management support Vikas Gupta
2025-06-19 13:39 ` Vadim Fedorenko
2025-06-24 10:31 ` Vikas Gupta
2025-06-18 14:47 ` [net-next, 08/10] bng_en: Add irq allocation support Vikas Gupta
2025-06-19 13:52 ` Vadim Fedorenko
2025-06-19 21:25 ` kernel test robot
2025-06-22 5:21 ` kernel test robot
2025-06-23 6:11 ` kernel test robot
2025-06-25 9:17 ` kernel test robot
2025-06-18 14:47 ` [net-next, 09/10] bng_en: Initialize default configuration Vikas Gupta
2025-06-18 20:16 ` kernel test robot
2025-06-19 13:57 ` Vadim Fedorenko
2025-06-20 9:08 ` kernel test robot
2025-06-22 12:39 ` kernel test robot
2025-06-26 8:47 ` kernel test robot
2025-06-18 14:47 ` [net-next, 10/10] bng_en: Add a network device Vikas Gupta
2025-06-24 0:42 ` kernel test robot
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=20250618144743.843815-1-vikas.gupta@broadcom.com \
--to=vikas.gupta@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=vsrama-krishna.nemani@broadcom.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
all inboxes | Powered by JetHome®