From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Zxyan Zhu <zxyan0222@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: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: stmmac: dwxgmac2: configure INTM for per-channel interrupt routing
Date: Wed, 29 Jul 2026 11:26:17 +0200 [thread overview]
Message-ID: <ac15d16e-1e3e-4b44-9e24-f12ef2e9d91c@bootlin.com> (raw)
In-Reply-To: <20260729023653.1162763-1-zxyan0222@gmail.com>
Hi
On 7/29/26 04:36, Zxyan Zhu wrote:
> The XGMAC DMA_MODE register has an INTM field (bits 13:12) that
> controls interrupt routing behavior for DMA transfer completion
> events:
>
> 00 (default): sbd_perch_* are pulse signals, sbd_intr_o is also
> asserted for each completion event.
> 01: sbd_perch_* are level signals, sbd_intr_o is NOT
> asserted for packet transfer completion events.
>
> When multi-MSI is enabled, per-channel TX/RX interrupts are expected
> to arrive on their dedicated lines. In the default INTM=00 mode,
> sbd_intr_o also fires for DMA completion events, but the multi-MSI
> handler stmmac_mac_interrupt() only processes MAC-layer events (LPI,
> PMT, timestamps) and returns IRQ_NONE for every DMA completion
> interrupt, resulting in a continuous stream of unhandled interrupts
> on the common IRQ.
>
> Hardware verification with XGMAC and multi-MSI enabled:
>
> INTM=00: 5.4 million common IRQ interrupts in 3 seconds, ~1.8
> million IRQ_NONE returns per second.
> INTM=01: 0 common IRQ interrupts, per-channel IRQs work normally,
> 10G line rate works correctly.
>
> Set INTM to mode 1 when multi-MSI is enabled. This matches the
> existing GMAC4 implementation.
>
> XGMAC multi-MSI has never worked correctly since it was introduced.
>
> Signed-off-by: Zxyan Zhu <zxyan0222@gmail.com>
Reviewed-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Maxime
> ---
> drivers/net/ethernet/stmicro/stmmac/dwxgmac2.h | 2 ++
> drivers/net/ethernet/stmicro/stmmac/dwxgmac2_dma.c | 10 ++++++++++
> 2 files changed, 12 insertions(+)
>
> diff --git a/drivers/net/ethernet/stmicro/stmmac/dwxgmac2.h b/drivers/net/ethernet/stmicro/stmmac/dwxgmac2.h
> index 61b6d45a02f5..f8ab347f7b5b 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/dwxgmac2.h
> +++ b/drivers/net/ethernet/stmicro/stmmac/dwxgmac2.h
> @@ -320,6 +320,8 @@
> /* DMA Registers */
> #define XGMAC_DMA_MODE 0x00003000
> #define XGMAC_SWR BIT(0)
> +#define XGMAC_INTM_MASK GENMASK(13, 12)
> +#define XGMAC_INTM_MODE1 0x1
> #define XGMAC_DMA_SYSBUS_MODE 0x00003004
> #define XGMAC_WR_OSR_LMT GENMASK(29, 24)
> #define XGMAC_RD_OSR_LMT GENMASK(21, 16)
> diff --git a/drivers/net/ethernet/stmicro/stmmac/dwxgmac2_dma.c b/drivers/net/ethernet/stmicro/stmmac/dwxgmac2_dma.c
> index 03437f1cf3df..ff83858ebc1f 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/dwxgmac2_dma.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/dwxgmac2_dma.c
> @@ -31,6 +31,16 @@ static void dwxgmac2_dma_init(void __iomem *ioaddr,
> value |= XGMAC_EAME;
>
> writel(value, ioaddr + XGMAC_DMA_SYSBUS_MODE);
> +
> + /*
> + * Route DMA interrupts to per-channel lines when multi-MSI enabled.
> + */
> + if (dma_cfg->multi_msi_en) {
> + value = readl(ioaddr + XGMAC_DMA_MODE);
> + value = u32_replace_bits(value, XGMAC_INTM_MODE1,
> + XGMAC_INTM_MASK);
> + writel(value, ioaddr + XGMAC_DMA_MODE);
> + }
> }
>
> static void dwxgmac2_dma_init_chan(struct stmmac_priv *priv,
>
> base-commit: 1df10cef2d1e7f9f2fb7eddb67fc70d3abf101f9
prev parent reply other threads:[~2026-07-29 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 2:36 [PATCH net-next v2] net: stmmac: dwxgmac2: configure INTM for per-channel interrupt routing Zxyan Zhu
2026-07-29 9:17 ` Qingfang Deng
2026-07-29 9:26 ` Maxime Chevallier [this message]
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=ac15d16e-1e3e-4b44-9e24-f12ef2e9d91c@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=zxyan0222@gmail.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