acpi_gpiochi...t_interrupts(9)

💅 acpi_gpiochip_request_interrupts ✨

okay so this is a page from the Kernel API Manual, section 9 — yes bestie, that's the (9) after the name, it's giving very much "kernel internals, handle with care" energy 🫶

---

🌸 NAME 🌸

acpi_gpiochip_request_interrupts — registers an isr for gpio chip ACPI events 💖 literally its whole personality.

---

✨ SYNOPSIS ✨

void acpi_gpiochip_request_interrupts(struct gpio_chip *chip);

that's it. that's the whole call. no return value, it's a void, she doesn't owe you a status code 💅

---

🎀 ARGUMENTS 🎀

• chip — the GPIO chip. like, the chip chip. the actual one. not a vibe, a struct gpio_chip *. 🌈

---

🦋 DESCRIPTION 🦋

okay so picture this: ACPI5 platforms can use GPIO signaled ACPI events — that's the whole thing, that's the tea ⭐

these GPIO interrupts get handled by ACPI event methods, and those methods need to be called from the GPIO chip's interrupt handler. iykyk. so acpi_gpiochip_request_interrupts goes and does the matchmaking 💖:

1. it finds out which GPIO pins actually have ACPI event methods attached to them 🔍
2. it assigns interrupt handlers for those pins 👑
3. those handlers call the ACPI event methods for the pins in question ✨

no cap, that's the entire job. she finds the pins, she wires up the handlers, she dips. main character energy fr fr 💀

---

👑 SEE ALSO 👑

• Kernel file ./drivers/gpio/gpiolib-acpi-core.c 📁
• struct acpi_gpio_event(9)
• struct acpi_gpio_info(9)
• acpi_get_gpiod(9)
• acpi_gpio_get_io_resource(9)
• acpi_gpiochip_free_interrupts(9) — the clean-up counterpart, they're a matched set 🫶
• acpi_get_gpiod_by_index(9)
• acpi_get_gpiod_from_data(9)
• acpi_dev_gpio_irq_wake_get_by(9)
• acpi_gpio_count(9)

---

that's the whole page bestie, go forth and register those interrupts 💜

🌷 sign-off time: this little number lives under ./drivers/gpio, dated October 2026, and answers to acpi_gpiochip_request_interrupts(9) 🎀 bye pookie, slay responsibly 💅✨