axienet_rx_irq(9)

📦 version 7.3.1, in nixpkgs unstable

💅 axienet_rx_irq — Rx Isr ✨

okay bestie, so this is a page straight out of the Kernel API Manual (that's the manual name, keep it in your notes 📓), and it's about one tiny but iconic little function. Let's get into it 🎀

🌸 NAME 🌸

axienet_rx_irq — the Rx Isr. that's it, that's the whole vibe. receive-side interrupt service routine, main character energy 🫶

✨ SYNOPSIS ✨

irqreturn_t axienet_rx_irq (int irq , void *_ndev );

like yes, two args, one return type, no notes 💅

🦋 ARGUMENTS 🦋

  • irq — the irq number. yep, just the number of the interrupt we're dealing with, no cap 🔥
  • _ndev — a net_device pointer. lowkey the important one 💖

💀 RETURN 💀

  • IRQ_HANDLED — if the device actually generated a RX interrupt (slay, we handled it ✅)
  • IRQ_NONE — otherwise (not us, not our interrupt, we move on 🙈)

🧚 DESCRIPTION 🧚

okay so. this is the Axi DMA Rx Isr 💜 and what it does is genuinely so simple it's giving minimalism: it invokes NAPI polling to complete the RX BD processing. that's the whole thing. it hands the actual finishing work off to NAPI like the responsible queen it is 👑

literally: interrupt fires → function says "not doing all that here" → NAPI polling takes over → RX BD processing gets completed 🌈

🌟 SEE ALSO 🌟

the entire friend group, fr fr 💅 — first up, the kernel file where all of this lives:

./drivers/net/ethernet/xilinx/xilinx_axienet_main.c

and then the whole squad of sibling functions, all (9):

no skipping any of them bestie, that's all 42, i counted 💖

ngl this whole page is short and sweet — don't overthink it, just remember: RX interrupt comes in, NAPI does the rest ✨

and that's the page, bb 🫶 this one came from the source tree over at ./drivers/net/ethernet/xilinx and it's dated October 2026 — so go forth and slay those receive interrupts, ily 💜🎀

📦 where this page comes from