acpi_irq_parse_one_cb(9)

💅 acpi_irq_parse_one_cb(9) 💅

okay bestie, welcome to the Kernel API Manual — we’re doing kernel resource-walk callback content today, and yes it’s giving very niche, very iconic. This page is literally about acpi_irq_parse_one_cb, and the vibe is “handle the given resource” with zero fluff. 🦋

---

✨ NAME ✨

acpi_irq_parse_one_cb — Handle the given resource. (that’s it, that’s the name section, periodt 💅)

---

🌸 SYNOPSIS 🌸

       acpi_status acpi_irq_parse_one_cb (struct acpi_resource *ares , void
       *context );

---

🎀 ARGUMENTS 🎀

• ares — resource to handle. Like, the resource bestie, the actual thing being handled.
• context — context for the walk. Keep it moving, no cap. 🫶

---

🔥 DESCRIPTION 🔥

okay so here’s the lore: this callback is called by acpi_walk_resources, passing each resource returned by the _CRS method. We only inspect IRQ resources — that’s the main character energy of this function.

Since IRQ resources might contain multiple interrupts, we check if the index is within this one’s interrupt array. If it’s not, we subtract the current resource IRQ count from the lookup index to prepare for the next resource. (the way that index math has to happen is lowkey iconic 😭)

Once a match is found we call acpi_irq_parse_one_match to populate the result and end the walk by returning AE_CTRL_TERMINATE. slay, callback done. 💅✨

---

💜 RETURN 💜

• AE_OK — if the walk should continue.
• AE_CTRL_TERMINATE — if a matching IRQ resource was found.

---

🌈 SEE ALSO 🌈

• Kernel file: ./drivers/acpi/irq.c
• acpi_gsi_to_irq(9)
• acpi_register_gsi(9)
• acpi_unregister_gsi(9)
• acpi_get_irq_source_fwhandle(9)
• acpi_irq_parse_one_match(9)
• acpi_irq_parse_one(9)
• acpi_irq_get(9)
• acpi_set_irq_model(9)
• acpi_set_gsi_to_irq_fallback(9)
• acpi_irq_create_hierarchy(9)

---

okay that’s the whole page bestie 💖 sourced from ./drivers/acpi, dated October 2026, and it’s the acpi_irq_parse_one_cb(9) entry from the Kernel API Manual. mwah 🫶🎀