From: Nicolai Buchwitz <nb@tipi-net.de>
To: netdev@vger.kernel.org
Cc: andrew+netdev@lunn.ch, claudiu.beznea@tuxon.dev,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
nicolas.ferre@microchip.com, pabeni@redhat.com,
linux@armlinux.org.uk, Nicolai Buchwitz <nb@tipi-net.de>
Subject: [PATCH net-next 0/5] net: cadence: macb: add IEEE 802.3az EEE support
Date: Mon, 23 Feb 2026 10:04:07 +0100 [thread overview]
Message-ID: <20260223090412.44070-1-nb@tipi-net.de> (raw)
Add Energy Efficient Ethernet (IEEE 802.3az) support to the Cadence GEM
(macb) driver. The GEM MAC has hardware LPI registers but no built-in
idle timer, so the driver implements software-managed TX LPI using a
delayed_work timer, as recommended by Microchip's GMAC documentation.
The series is structured as follows:
1. Register definitions: LPI counter offsets (0x270-0x27c), TXLPIEN
bitfield (NCR bit 19), and a MACB_CAPS_EEE capability flag.
2. LPI statistics: Expose the four hardware EEE counters (RX/TX LPI
transitions and time) through ethtool -S, accumulated in software
since they are clear-on-read.
3. TX LPI engine: A delayed_work-based idle timer that enters LPI
after 250ms of TX inactivity and wakes before transmit with a
conservative 50us PHY wake delay. LPI entry is deferred 1 second
after link-up per IEEE 802.3az.
4. ethtool EEE ops: get_eee/set_eee delegating to phylink for PHY
negotiation; the MAC-level TXLPIEN is controlled only from the
phylink mac_link_up/mac_link_down callbacks.
5. RP1 enablement: Set MACB_CAPS_EEE for the Raspberry Pi 5's RP1
southbridge (Cadence GEM_GXL rev 0x00070109 + BCM54213PE PHY).
Tested on Raspberry Pi 5 with iperf3 throughput/latency benchmarks,
ethtool --show-eee / --set-eee, ethtool -S LPI counter verification,
and cable unplug/replug cycling.
Nicolai Buchwitz (5):
net: cadence: macb: add EEE register definitions and capability flag
net: cadence: macb: add EEE LPI statistics counters
net: cadence: macb: implement EEE TX LPI support
net: cadence: macb: add ethtool EEE support
net: cadence: macb: enable EEE for Raspberry Pi RP1
drivers/net/ethernet/cadence/macb.h | 23 ++++
drivers/net/ethernet/cadence/macb_main.c | 160 ++++++++++++++++++++++-
2 files changed, 180 insertions(+), 3 deletions(-)
--
2.39.5
next reply other threads:[~2026-02-23 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 9:04 Nicolai Buchwitz [this message]
2026-02-23 9:04 ` [PATCH net-next 1/5] net: cadence: macb: add EEE register definitions and capability flag Nicolai Buchwitz
2026-02-23 9:04 ` [PATCH net-next 2/5] net: cadence: macb: add EEE LPI statistics counters Nicolai Buchwitz
2026-02-23 9:04 ` [PATCH net-next 3/5] net: cadence: macb: implement EEE TX LPI support Nicolai Buchwitz
2026-02-23 10:07 ` Russell King (Oracle)
2026-02-23 14:54 ` nb
2026-02-23 9:04 ` [PATCH net-next 4/5] net: cadence: macb: add ethtool EEE support Nicolai Buchwitz
2026-02-23 9:04 ` [PATCH net-next 5/5] net: cadence: macb: enable EEE for Raspberry Pi RP1 Nicolai Buchwitz
2026-02-23 9:14 ` [PATCH net-next 0/5] net: cadence: macb: add IEEE 802.3az EEE support Russell King (Oracle)
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=20260223090412.44070-1-nb@tipi-net.de \
--to=nb@tipi-net.de \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.beznea@tuxon.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.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