From: Daniel Golle <daniel@makrotopia.org>
To: Frank Wunderlich <linux@fw-web.de>
Cc: Felix Fietkau <nbd@nbd.name>, Sean Wang <sean.wang@mediatek.com>,
Lorenzo Bianconi <lorenzo@kernel.org>,
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>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Frank Wunderlich <frank-w@public-files.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Simon Horman <horms@kernel.org>,
arinc.unal@arinc9.com
Subject: Re: [net-next v5 3/3] net: ethernet: mtk_eth_soc: skip first IRQ if not used
Date: Wed, 18 Jun 2025 19:41:50 +0200 [thread overview]
Message-ID: <aFL6XhghHobju0th@pidgin.makrotopia.org> (raw)
In-Reply-To: <20250618130717.75839-4-linux@fw-web.de>
On Wed, Jun 18, 2025 at 03:07:14PM +0200, Frank Wunderlich wrote:
> From: Frank Wunderlich <frank-w@public-files.de>
>
> On SoCs without MTK_SHARED_INT capability (all except mt7621 and
> mt7628) platform_get_irq() is called for the first IRQ (eth->irq[0])
> but it is never used.
I know that technically MTK_SHARED_INT is a capability flag, but it's
rather a non-capability. Hardware having dedicated interrupts for RX and
TX is "more capable" than (older, legacy) hardware with just one shared
interrupt for both...
So maybe better:
"On SoCs with dedicated RX and TX interrupts (all except MT7621 and
MT7628) ..."
Reading the datasheet of some recent MediaTek SoC it is worth
noting that there are 4 interrupts assigned to the frame engine and
the FE_INT_GRP register can be used to assign functions to them.
So technically, calling them RX and TX in DT is wrong, becaues they
are fe_int0, fe_int1, fe_int2 and fe_int3, which are then assigned
one or more functions by the driver using that FE_INT_GRP register.
However, it's the driver then assigns QDMA TX to fe_int1 and RX to
fe_int2 while leaving fe_int0 and fe_int3 unsued.
That's what the magic value 0x21021000 which is written to FE_INT_GRP
register does.
On MT7988 and newer, in addition to those 4 frame engine interrupts
there are **another 4** interrupts for PDMA, typically used to
service 4 RX rings while one of the fe_int* is used to indicate
TX done.
> Skip the first IRQ and reduce the IRQ-count to 2.
>
> Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
> ---
> v5:
> - change commit title and description
> v4:
> - drop >2 condition as max is already 2 and drop the else continue
> - update comment to explain which IRQs are taken in legacy way
> ---
> drivers/net/ethernet/mediatek/mtk_eth_soc.c | 12 ++++++++----
> drivers/net/ethernet/mediatek/mtk_eth_soc.h | 4 ++--
> 2 files changed, 10 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/ethernet/mediatek/mtk_eth_soc.c b/drivers/net/ethernet/mediatek/mtk_eth_soc.c
> index 875e477a987b..7990c84b2b56 100644
> --- a/drivers/net/ethernet/mediatek/mtk_eth_soc.c
> +++ b/drivers/net/ethernet/mediatek/mtk_eth_soc.c
> @@ -3354,10 +3354,14 @@ static int mtk_get_irqs(struct platform_device *pdev, struct mtk_eth *eth)
> * the second is for TX, and the third is for RX.
> */
> for (i = 0; i < MTK_FE_IRQ_NUM; i++) {
> - if (MTK_HAS_CAPS(eth->soc->caps, MTK_SHARED_INT) && i > 0)
> - eth->irq[i] = eth->irq[MTK_FE_IRQ_SHARED];
> - else
> - eth->irq[i] = platform_get_irq(pdev, i);
> + if (MTK_HAS_CAPS(eth->soc->caps, MTK_SHARED_INT)) {
> + if (i == 0)
This would make it even more readable:
if (i == MTK_FE_IRQ_SHARED)
Other than that looks good to me:
Reviewed-by: Daniel Golle <daniel@makrotopia.org>
> + eth->irq[MTK_FE_IRQ_SHARED] = platform_get_irq(pdev, i);
> + else
> + eth->irq[i] = eth->irq[MTK_FE_IRQ_SHARED];
> + } else {
> + eth->irq[i] = platform_get_irq(pdev, i + 1);
> + }
>
> if (eth->irq[i] < 0) {
> dev_err(&pdev->dev, "no IRQ%d resource found\n", i);
> diff --git a/drivers/net/ethernet/mediatek/mtk_eth_soc.h b/drivers/net/ethernet/mediatek/mtk_eth_soc.h
> index 8cdf1317dff5..9261c0e13b59 100644
> --- a/drivers/net/ethernet/mediatek/mtk_eth_soc.h
> +++ b/drivers/net/ethernet/mediatek/mtk_eth_soc.h
> @@ -643,8 +643,8 @@
> #define MTK_MAC_FSM(x) (0x1010C + ((x) * 0x100))
>
> #define MTK_FE_IRQ_SHARED 0
> -#define MTK_FE_IRQ_TX 1
> -#define MTK_FE_IRQ_RX 2
> +#define MTK_FE_IRQ_TX 0
> +#define MTK_FE_IRQ_RX 1
> #define MTK_FE_IRQ_NUM (MTK_FE_IRQ_RX + 1)
>
> struct mtk_rx_dma {
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2025-06-18 19:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 13:07 [net-next v5 0/3] rework IRQ handling in mtk_eth_soc Frank Wunderlich
2025-06-18 13:07 ` [net-next v5 1/3] net: ethernet: mtk_eth_soc: support named IRQs Frank Wunderlich
2025-06-18 13:55 ` Daniel Golle
2025-06-18 14:50 ` Frank Wunderlich
2025-06-18 13:07 ` [net-next v5 2/3] net: ethernet: mtk_eth_soc: add consts for irq index Frank Wunderlich
2025-06-18 14:23 ` Daniel Golle
2025-06-18 13:07 ` [net-next v5 3/3] net: ethernet: mtk_eth_soc: skip first IRQ if not used Frank Wunderlich
2025-06-18 17:41 ` Daniel Golle [this message]
2025-06-19 10:03 ` Simon Horman
2025-06-19 10:32 ` Aw: " Frank Wunderlich
2025-06-19 12:51 ` Simon Horman
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=aFL6XhghHobju0th@pidgin.makrotopia.org \
--to=daniel@makrotopia.org \
--cc=andrew+netdev@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arinc.unal@arinc9.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frank-w@public-files.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@fw-web.de \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.wang@mediatek.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;
as well as URLs for NNTP newsgroup(s).