acpi_pci_link_allocate_irq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the Kernel API Manual πŸ’– this one lives in section 9 and it's literally called acpi_pci_link_allocate_irq β€” say that five times fast, i dare you 🫢


🌸 NAME 🌸

acpi_pci_link_allocate_irq β€” Retrieve a link device GSI ⚑


πŸŽ€ SYNOPSIS πŸŽ€

int acpi_pci_link_allocate_irq (acpi_handle handle , int index , int
*triggering , int *polarity , char **name , u32 *gsi );

like, that's the whole vibe right there πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • handle β€” the handle for the link device, aka your main character πŸ”‘
  • index β€” the GSI index, it's giving "which one tho" πŸ”’
  • triggering β€” a pointer to store the GSI trigger, so it can remember how it's triggered πŸ’…
  • polarity β€” a pointer to store GSI polarity, because everything has two sides bestie βš–οΈ
  • name β€” a pointer to store the link device name, so it knows what to call itself 🏷️
  • gsi β€” a pointer to store the GSI number, the actual digits, no cap πŸ”₯

πŸ’œ RETURN πŸ’œ

  • 0 on success β€” and when it slays, it comes with triggering, polarity, name, gsi all initialized ✨
  • -ENODEV on failure β€” it's giving "no device found", huge L, we don't talk about it 😭

🧚 SEE ALSO 🧚

  • Kernel file ./drivers/acpi/pci_link.c β€” go read it, iykyk πŸ“–

and that's the whole page bestie, no notes πŸ’… fr fr β€” this lil manual page is from ./drivers/acpi, dated October 2026, and it's the acpi_pci_link_allocate_irq(9) entry, so like, cite it properly in your kernel homework and you'll ate that πŸŽ“β­ πŸ¦‹ 🌈 πŸ“ πŸ‘‘

πŸ“¦ where this page comes from