enable_irq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ enable_irq β€” like, the Kernel API Manual energy ✨

okay bestie, we're in the enable_irq(9) girlies today πŸ’… this one's short and sweet, no cap.


🌸 NAME 🌸

enable_irq β€” enables the handling of an irq πŸ”₯ (yes, that's the whole job, and she does it well)


πŸŽ€ SYNOPSIS πŸŽ€

void enable_irq (unsigned int irq );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • irq β€” the interrupt you wanna enable, periodt ✨

πŸ’– DESCRIPTION πŸ’–

So basically? This function undoes the effect of one single call to disable_irq. One call, one undo β€” they're matched, iykyk 🫢

And if this happens to match the last disable? That's when the processing of interrupts on this IRQ line gets re-enabled. slay. the gates are open again πŸ’…βœ¨

⚠️ okay important caveat bestie, don't skip this: this function may be called from IRQ context only when desc->irq_data.chip->bus_lock and desc->chip->bus_sync_unlock are NULL ! Like, both of them. NULL. Otherwise? not the vibe, don't do it 😭

🌈 SEE ALSO 🌈

Kernel file ./kernel/irq/manage.c β€” and here's the whole friend group, literally all of them, no one left out 🫢:


okay that's the whole page bestie, go turn some interrupts back on πŸ’œ

so yeah β€” this drop lives under ./kernel/irq and it's dated October 2026, brought to you by the enable_irq(9) girlies themselves πŸ§šβ€β™€οΈ mwah, bye πŸŽ€

πŸ“¦ where this page comes from