From: Greg KH <gregkh@linuxfoundation.org>
To: Ovidiu Panait <ovidiu.panait.rb@renesas.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 6.18.y 0/1] net: stmmmac: Fix lpi_intr_o interrupt storms
Date: Mon, 9 Mar 2026 14:42:09 +0100 [thread overview]
Message-ID: <2026030900-twitch-maternity-1792@gregkh> (raw)
In-Reply-To: <20260306150502.23713-1-ovidiu.panait.rb@renesas.com>
On Fri, Mar 06, 2026 at 03:05:01PM +0000, Ovidiu Panait wrote:
> Backport upstream commit 14eb64db8ff0 ("net: stmmac: remove support
> for lpi_intr_o"), to fix Ethernet interrupt storms on the Renesas RZ/V2H
> and RZ/V2N platforms.
>
> The stmmac lpi_intr_o sideband signal is synchronous to the PHY RX clock,
> which can be stopped by the link partner while the interrupt is still
> asserted, causing an interrupt storm. Since the lpi_intr_o interrupt
> serves no useful purpose and it causes issues, it was removed in mainline.
>
> Russell King (Oracle) (1):
> net: stmmac: remove support for lpi_intr_o
> drivers/net/ethernet/stmicro/stmmac/common.h | 1 -
> .../net/ethernet/stmicro/stmmac/dwmac-intel.c | 4 ---
> .../ethernet/stmicro/stmmac/dwmac-loongson.c | 7 ----
> drivers/net/ethernet/stmicro/stmmac/stmmac.h | 2 --
> .../net/ethernet/stmicro/stmmac/stmmac_main.c | 36 -------------------
> .../ethernet/stmicro/stmmac/stmmac_platform.c | 8 -----
> include/linux/stmmac.h | 1 -
> 7 files changed, 59 deletions(-)
>
> --
> 2.34.1
>
>
What about 6.19.y?
next prev parent reply other threads:[~2026-03-09 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 15:05 [PATCH 6.18.y 0/1] net: stmmmac: Fix lpi_intr_o interrupt storms Ovidiu Panait
2026-03-06 15:05 ` [PATCH 6.18.y 1/1] net: stmmac: remove support for lpi_intr_o Ovidiu Panait
2026-03-09 13:42 ` Greg KH [this message]
2026-03-09 14:15 ` [PATCH 6.18.y 0/1] net: stmmmac: Fix lpi_intr_o interrupt storms Ovidiu Panait
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=2026030900-twitch-maternity-1792@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ovidiu.panait.rb@renesas.com \
--cc=stable@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