From: mike.marciniszyn@gmail.com
To: Lee Jones <lee@kernel.org>, Pavel Machek <pavel@kernel.org>,
Alexander Duyck <alexanderduyck@fb.com>,
Jakub Kicinski <kuba@kernel.org>,
kernel-team@meta.com, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Russell King <linux@armlinux.org.uk>,
Daniel Golle <daniel@makrotopia.org>, Kees Cook <kees@kernel.org>,
Simon Horman <horms@kernel.org>,
Dimitri Daskalakis <dimitri.daskalakis1@gmail.com>,
Jacob Keller <jacob.e.keller@intel.com>,
Lee Trager <lee@trager.us>,
Mohsin Bashir <mohsin.bashr@gmail.com>,
Alok Tiwari <alok.a.tiwari@oracle.com>,
Chengfeng Ye <dg573847474@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Andrew Lunn <andrew@lunn.ch>
Cc: mike.marciniszyn@gmail.com, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH net-next 0/3] dd LED support for fbnic
Date: Wed, 20 May 2026 16:03:34 -0400 [thread overview]
Message-ID: <20260520200337.204431-1-mike.marciniszyn@gmail.com> (raw)
From: "Mike Marciniszyn (Meta)" <mike.marciniszyn@gmail.com>
Add support for fbnic leds in three patches.
The first patch adds the trigger support for the higher
fbnic speeds.
The second patch stors the max speed from the firmware dialog
to give the LED code a way to determine if the led needs to show
amber (not full speed) or blue (at full speed).
The third patch adds the fbnic specific code to manipulate the LEDS
as well as the /sys/class/leds support for user space access.
Mike Marciniszyn (Meta) (3):
leds: trigger: netdev: Extend speeds up to 100G
net: eth: fbnic: Store max_speed from firmware dialog
net: eth: fbnic: Add led support
drivers/leds/trigger/ledtrig-netdev.c | 46 +++-
drivers/net/ethernet/meta/Kconfig | 8 +
drivers/net/ethernet/meta/fbnic/Makefile | 2 +
drivers/net/ethernet/meta/fbnic/fbnic.h | 13 +
drivers/net/ethernet/meta/fbnic/fbnic_csr.h | 15 ++
.../net/ethernet/meta/fbnic/fbnic_devlink.c | 4 +
.../net/ethernet/meta/fbnic/fbnic_ethtool.c | 59 +++++
drivers/net/ethernet/meta/fbnic/fbnic_fw.c | 3 +
drivers/net/ethernet/meta/fbnic/fbnic_fw.h | 3 +
drivers/net/ethernet/meta/fbnic/fbnic_led.c | 228 +++++++++++++++++
drivers/net/ethernet/meta/fbnic/fbnic_mac.c | 239 ++++++++++++++++++
drivers/net/ethernet/meta/fbnic/fbnic_mac.h | 62 +++++
drivers/net/ethernet/meta/fbnic/fbnic_pci.c | 8 +
.../net/ethernet/meta/fbnic/fbnic_phylink.c | 2 +
include/linux/leds.h | 4 +
15 files changed, 695 insertions(+), 1 deletion(-)
create mode 100644 drivers/net/ethernet/meta/fbnic/fbnic_led.c
--
2.43.0
next reply other threads:[~2026-05-20 20:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 20:03 mike.marciniszyn [this message]
2026-05-20 20:03 ` [PATCH net-next 1/3] leds: trigger: netdev: Extend speeds up to 100G mike.marciniszyn
2026-05-20 20:16 ` Andrew Lunn
2026-06-11 14:20 ` Lee Jones
2026-06-11 15:19 ` Andrew Lunn
2026-06-18 11:01 ` (subset) " Lee Jones
2026-05-20 20:03 ` [PATCH net-next 2/3] net: eth: fbnic: Store max_speed from firmware dialog mike.marciniszyn
2026-05-20 20:03 ` [PATCH net-next 3/3] net: eth: fbnic: Add led support mike.marciniszyn
2026-05-20 20:37 ` Andrew Lunn
2026-05-21 14:05 ` Mike Marciniszyn
2026-05-21 17:15 ` Andrew Lunn
2026-05-20 20:14 ` [PATCH net-next 0/3] dd LED support for fbnic Andrew Lunn
2026-05-21 11:03 ` Lee Jones
2026-05-21 11:59 ` Andrew Lunn
2026-05-21 13:33 ` Lee Jones
2026-06-02 21:34 ` Andy Shevchenko
2026-05-21 14:13 ` Mike Marciniszyn
2026-05-21 14:28 ` Andrew Lunn
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=20260520200337.204431-1-mike.marciniszyn@gmail.com \
--to=mike.marciniszyn@gmail.com \
--cc=alexanderduyck@fb.com \
--cc=alok.a.tiwari@oracle.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dg573847474@gmail.com \
--cc=dimitri.daskalakis1@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kees@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=lee@trager.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavel@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
all inboxes | Powered by JetHome®