Re: [PATCH RFC 0/3] genirq: Allow drivers to respect userspace IRQ affinities

From
Andrew Lunn <andrew@lunn.ch>
Date
2026-08-19 23:55:31
Also in
linux-arm-kernel, linux-rt-devel, lkml
Reply to
Florian Bezdeka, 2026-08-19
That raises the question why request_irq() is called on "link up" time,
while the low level vector allocation takes place during device probing.
If the interface is admin down, the hardware should not be generating
any interrupts. So there is no need to request them.
At least that seems to be the common pattern. Can someone tell me why
this is done this way? Shouldn't we call request_irq() at the same time?
If you want to change anything, move the low level vector allocation
into open(). But you need to be careful of EPROBE_DEFER. If the
interrupt controller has not loaded yet, i _guess_ the low level
vector allocation will return EPROBE_DEFER, and the MAC driver will
try to probe again later. If you get EPROBE_DEFER in open(), there is
nothing you can do about it.

	Andrew
Thread (21 messages) 21 messages, 6 authors, last reply 2026-08-21
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help