From: Qingfang Deng <qingfang.deng@linux.dev>
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: Maxime Chevallier <maxime.chevallier@bootlin.com>,
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 17:17:05 +0800 [thread overview]
Message-ID: <d469bc41-c3bd-4442-92d4-ec2b87e7ad98@linux.dev> (raw)
In-Reply-To: <20260729023653.1162763-1-zxyan0222@gmail.com>
On 2026/7/29 10: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>
As someone who has written an out-of-tree driver for the DW XGMAC:
Reviewed-by: Qingfang Deng <qingfang.deng@linux.dev>
next prev parent reply other threads:[~2026-07-29 9:17 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 [this message]
2026-07-29 9:26 ` Maxime Chevallier
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=d469bc41-c3bd-4442-92d4-ec2b87e7ad98@linux.dev \
--to=qingfang.deng@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--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