acpi_dev_irq_flags(9)

📦 version 7.3.1, in nixpkgs unstable

💅 acpi_dev_irq_flags(9) — a Kernel API Manual moment

okay so bestie, welcome to the Kernel API Manual, section 9, and today's main character is acpi_dev_irq_flags 🎀 she's not flashy, but she's literally the one who tells you what your IRQ flags should be, and honestly? we stan a quiet achiever.

✨ NAME ✨

acpi_dev_irq_flags — determine IRQ resource flags 💖

like, that's her whole job. she determines the flags. for IRQ resources. no cap.

🌸 SYNOPSIS 🌸

unsigned long acpi_dev_irq_flags (u8 triggering , u8 polarity , u8
       shareable , u8 wake_capable );

she takes four u8 besties in and hands you back an unsigned long, which is giving "trust the process" energy tbh 🔥

🦋 ARGUMENTS 🦋

  • triggering — the triggering type, exactly as ACPI handed it over. don't overthink it, she got it from ACPI 💅
  • polarity — the interrupt polarity, again as provided by ACPI. yes, both of these come straight from ACPI, she's just the messenger 🫶
  • shareable — whether or not the interrupt is shareable. that's it. that's the whole vibe check ✨
  • wake_capable — wake capability, as provided by ACPI. so like, can it wake you up? ACPI says so, not her 🙈
ngl bestie, all four of these are just "as provided by ACPI" — she's a translator, not a decision maker. respect the pipeline 👑

👑 SEE ALSO 👑

the kernel file dossier lives at ./drivers/acpi/resource.c, and honestly the whole friend group is here, go say hi 🥰

like, that's the whole group chat. every single one of them. don't leave anyone on read 💀

okay that's the page!! and before you go — huge shoutout to ./drivers/acpi for being the home directory of all this chaos, dated October 2026, because yes she's from the future and she's still determining flags 🌈💜

slay, go read some ACPI resources, and remember: the flags were in you all along ✨🎀🦋

📦 where this page comes from