acpi_irq_parse_one(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

acpi_irq_parse_one — the glow-up where we figure out which interrupt a device is actually using 💅

okay so first things first, the manual name is Kernel API Manual (yes that's the vibe, we're in kernel-land now bestie) and this whole page is literally about Resolve an interrupt for a device. Iconic.

✨ SYNOPSIS ✨

int acpi_irq_parse_one (acpi_handle handle , unsigned int index , struct
       irq_fwspec *fwspec , unsigned long *flags );

🎀 ARGUMENTS 🎀

  • handle — the device whose interrupt we're resolving, aka our main character for this function call 🫶
  • index — which interrupt to resolve, like picking which one of the group chat's 47 unread messages you're actually gonna reply to
  • fwspec — a struct irq_fwspec that this function fills in for you. she's getting populated while you watch, periodt
  • flags — the resource flags, also filled in by this function. yes bestie, two output things, she's generous 💖

🌸 DESCRIPTION 🌸

So here's the tea ☕ — acpi_irq_parse_one resolves an interrupt for a device by walking its CRS resources to find the appropriate ACPI IRQ resource, and then populating the given struct irq_fwspec and flags.

that's it. that's the whole vibe. she walks the CRS resources, she finds the right ACPI IRQ resource, she fills in your structs and flags. no notes. 🌈

⭐ RETURN ⭐

The result stored in ctx.rc by the callback — or the default -EINVAL value if an error occurs 😭

ngl if you see -EINVAL coming back, something went sideways in the callback ✨

🦋 SEE ALSO 🦋

Kernel file ./drivers/acpi/irq.c — the whole squad lives here, go say hi 💜

k bye bestie, stay resolving 💅✨ this one came straight out of ./drivers/acpi and it's dated October 2026 — so go forth, parse those interrupts, and slay 👑🌸

📦 where this page comes from