acpi_get_irq...rce_fwhandle(9)

📦 version 7.3.1, in nixpkgs unstable

💖 acpi_get_irq...rce_fwhandle(9) 💖

okay bestie, so this is a page from the Kernel API Manual — yes, that manual, the kernel one, we're in the big leagues now 🫶 — and it's genuinely short and sweet, so grab a strawberry 🍓 and let's go.

✨ NAME ✨

acpi_get_irq_source_fwhandle — Retrieve fwhandle from IRQ resource source.

like, the whole personality of this function is "give me the source, I'll give you the handle" and honestly? iconic. 👑

🌸 SYNOPSIS 🌸

struct fwnode_handle * acpi_get_irq_source_fwhandle (const struct
       acpi_resource_source *source , u32 gsi );

one function, two arguments, zero drama. look at that return type — it's giving struct fwnode_handle * main character energy 💅

🦋 ARGUMENTS 🦋

  • source — the acpi_resource_source you're using for the lookup. yeah, this one. it's your search key, bestie 🔍
  • gsi — the GSI IRQ number. it's a u32, it's a number, it's doing its job. no notes ✨

🎀 DESCRIPTION 🎀

So what does it actually do, you ask? It retrieves the fwhandle of the device referenced by the given IRQ resource source. that's it. that's the vibe check. literally just fetching the firmware handle for the device that the IRQ resource source points at. simple, clean, slay. 💖

🌈 RETURN 🌈

It hands you back the referenced device fwhandle, or NULL on failure. so like… check for NULL, okay? don't be that person who forgets and then everything explodes 😭 lowkey important.

fr fr, a NULL return means failure. that's not a hint, that's the contract. handle it. 🙈

💜 SEE ALSO 💜

Kernel file ./drivers/acpi/irq.c, plus the whole friend group of ACPI IRQ functions — go say hi to all of them, they're all linked here and they all matter:

and that's the whole page, bestie — short, sweet, and fully documented 🧚✨

sign-off time: this one lives in ./drivers/acpi, and it's dated October 2026. go off, kernel girlies 💅🎀🔥

📦 where this page comes from