request_irq(9)

🌸 request_irq(9) — the kernel API manual, bestie edition 🌸

okay so real talk, this one lives in section 9 of the kernel API manual and it's literally the "hey kernel, wake me up when the hardware tugs on this wire" function 💅

✨ NAME ✨

request_irq — add a handler for an interrupt line 🎀

🦋 SYNOPSIS 🦋

int request_irq (unsigned int irq , irq_handler_t handler , unsigned
long flags , const char *name , void *dev );

like yes bestie, that's the whole signature, no cap ✨

💖 ARGUMENTS 💖

• irq — the interrupt line you're allocating. this is the actual wire you're claiming, so be normal about it 🫶
• handler — the function that gets called when the IRQ occurs. it's the primary handler for threaded interrupts. and if you pass NULL? the default primary handler gets installed instead, iconic default behavior 💅
• flags — the handling flags. all of them. the vibes of how this interrupt gets handled 🌈
• name — the name of the device generating this interrupt. you know, so people know whose interrupt this is 👑
• dev — a cookie passed to the handler function 🍓 (yes, a cookie. it's for you. hold onto it.)

🧚 DESCRIPTION 🧚

so this call allocates an interrupt and establishes a handler — both, in one go, main character energy fr fr 🔥

for the full deets though? see the documentation for request_threaded_irq. that's where the details live, iykyk 💜

⭐ SEE ALSO ⭐

• Kernel file ./include/linux/interrupt.h
• struct irqaction(9)
• struct irq_affinity_notify(9)
• struct irq_affinity(9)
• struct irq_affinity_desc(9)
• irq_update_affinity_hint(9)
• irq_set_affinity_and_hint(9)

k that's the whole page bestie, mwah 💋 this one's from ./include/linux, dated October 2026, and it's request_irq(9) — go interrupt something slay 💖✨