acpi_dev_resource_interrupt(9)

📦 version 7.3.1, in nixpkgs unstable

okay bestie, welcome to the acpi_dev_resource_interrupt(9) page from the Kernel API Manual 💅✨ This is the one that extracts ACPI interrupt resource info, and it's lowkey iconic.

🌸 NAME 🌸

acpi_dev_resource_interrupt — Extract ACPI interrupt resource information.

🦋 SYNOPSIS 🦋

bool acpi_dev_resource_interrupt (struct acpi_resource *ares , int index
       , struct resource *res );

🎀 ARGUMENTS 🎀

  • ares — input ACPI resource object. This is the resource we're checking, bestie.
  • index — index into the array of GSIs represented by the resource. Basically which GSI slot we're looking at.
  • res — output generic resource object. This is the output glow-up spot.

💜 DESCRIPTION 💜

Check if the given ACPI resource object represents an interrupt resource and index does not exceed the resource's interrupt count — and true is returned in that case regardless of the results of the other checks, no cap. If that's the case, register the GSI corresponding to index from the array of interrupts represented by the resource and populate the generic resource object pointed to by res accordingly. If the registration of the GSI is not successful, IORESOURCE_DISABLED will be set it that object's flags — yes, that's the exact wording, and we are keeping every detail 💀✨

🔥 RETURN 🔥

Okay, the return-value vibe check is literally:

  1. false with res->flags setting to zero: not the expected resource type.
  2. false with IORESOURCE_DISABLED in res->flags: valid unassigned resource.
  3. true: valid assigned resource.

🌈 SEE ALSO 🌈

Kernel file ./drivers/acpi/resource.c plus the whole friend group:

mwah 💋 source/version ./drivers/acpi · date October 2026 · page acpi_dev_resource_interrupt(9) — bestie, that's the whole page, go be the main character of ACPI interrupt resources 🎀🫶✨

📦 where this page comes from