From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Zhou, Yun" <yun.zhou@windriver.com>
Cc: marcin.s.wojtas@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, maxime.chevallier@bootlin.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] net: mvneta: re-enable percpu interrupt on resume
Date: Wed, 24 Jun 2026 11:32:18 +0200 [thread overview]
Message-ID: <20260624093218.G7t8fj4a@linutronix.de> (raw)
In-Reply-To: <52e2dc9b-45ce-4779-8ca3-b4e022380db6@windriver.com>
On 2026-06-19 09:15:05 [+0800], Zhou, Yun wrote:
> This is a hardware constraint, not a software design choice.
>
…
> This means request_percpu_irq() is the only valid registration
> method — a plain request_irq() would fail with -EINVAL because the
> irq descriptor requires IRQ_PER_CPU_DEVID semantics.
…
> The multi-interrupt approach (like MSI-X NICs) would require the
> hardware to provide multiple distinct interrupt lines per port,
> which this SoC does not have.
I don't question that. There might have been an option route that
interrupt source differently. If it is not the case, then there is not
much you can do. Thank you for the explanation.
> BR,
> Yun
Sebastian
prev parent reply other threads:[~2026-06-24 9:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 10:43 [PATCH v3] net: mvneta: re-enable percpu interrupt on resume Yun Zhou
2026-06-18 12:51 ` Sebastian Andrzej Siewior
2026-06-18 13:56 ` Zhou, Yun
2026-06-18 15:04 ` Sebastian Andrzej Siewior
2026-06-18 15:34 ` Maxime Chevallier
2026-06-18 15:45 ` Zhou, Yun
2026-06-18 15:53 ` Sebastian Andrzej Siewior
2026-06-19 1:15 ` Zhou, Yun
2026-06-24 9:32 ` Sebastian Andrzej Siewior [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=20260624093218.G7t8fj4a@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.s.wojtas@gmail.com \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yun.zhou@windriver.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