From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Nicolai Buchwitz <nb@tipi-net.de>,
Doug Berger <opendmb@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: bcm-kernel-feedback-list@broadcom.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: bcmgenet: enable EEE TX LPI by default
Date: Mon, 16 Mar 2026 12:54:46 -0700 [thread overview]
Message-ID: <997daf22-260b-40c4-a2d6-8c63f59df9a7@broadcom.com> (raw)
In-Reply-To: <20260303160225.542613-1-nb@tipi-net.de>
On 3/3/26 08:02, Nicolai Buchwitz wrote:
> GENET never initializes priv->eee.eee_enabled or
> priv->eee.tx_lpi_enabled to true, so the link-change callback in
> bcmgenet_mac_config() always calls bcmgenet_eee_enable_set() with
> enable=false. The result is that EEE is negotiated at the PHY level
> but the MAC never enters Low Power Idle, wasting the power savings
> that EEE is designed to provide.
>
> Users can work around this with 'ethtool --set-eee eth0 eee on tx-lpi
> on tx-timer 250', but the MAC should enable TX LPI out of the box when
> the hardware supports it, consistent with how phylink-managed MACs
> behave (phylink calls phy_support_eee() which sets eee_enabled=true and
> tx_lpi_enabled=true by default).
>
> Initialize EEE software state during bcmgenet_open() on GENET v2+ so
> that the link-change path activates EEE in hardware once the PHY
> negotiates it. Use an LPI timer of 250 us, matching the default used
> by other MAC drivers (mvneta, mvpp2).
>
> Signed-off-by: Nicolai Buchwitz <nb@tipi-net.de>
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
--
Florian
next prev parent reply other threads:[~2026-03-16 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 16:02 [PATCH net-next] net: bcmgenet: enable EEE TX LPI by default Nicolai Buchwitz
2026-03-16 19:54 ` Florian Fainelli [this message]
2026-03-16 20:59 ` Jakub Kicinski
2026-03-16 21:21 ` Florian Fainelli
2026-03-17 7:51 ` Nicolai Buchwitz
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=997daf22-260b-40c4-a2d6-8c63f59df9a7@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.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