acpi_register_gsi(9)
π acpi_register_gsi β the kernel API manual, but make it make sense π
okay so bestie, welcome to acpi_register_gsi(9) from the Kernel API Manual. no cap, this one is short and sweet and honestly kind of iconic. it's the little function that maps a GSI to a linux IRQ number. let me break it down π
β¨ NAME β¨
acpi_register_gsi β literally the function that maps a GSI to a linux IRQ number π
β¨ SYNOPSIS β¨
int acpi_register_gsi (struct device *dev , u32 gsi , int trigger , int
polarity );
look at her. four arguments, one int return, no drama. we stan a tidy signature π«Ά
β¨ ARGUMENTS β¨
devβ the device for which the IRQ has to be mapped. it's giving "who is this for" energy πΈgsiβ the GSI IRQ number, i.e. the thing you're mapping πtriggerβ the trigger type of the GSI number to be mapped β‘polarityβ the polarity of the GSI to be mapped π§
like yes ma'am, four little params and every single one matters π
β¨ RETURN β¨
on success you get a valid linux IRQ number π and on failure you get -EINVAL π (bestie check your inputs, fr fr).
β¨ SEE ALSO β¨
living in the kernel file ./drivers/acpi/irq.c, and here's the whole friend group π:
acpi_gsi_to_irq(9)acpi_unregister_gsi(9)acpi_get_irq_source_fwhandle(9)acpi_irq_parse_one_match(9)acpi_irq_parse_one_cb(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)
and that's the whole page, no notes π₯ this little beauty lives in ./drivers/acpi and the version stamped on her is October 2026. go map some IRQs, bestie, you're gonna slay π¦βπ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms