acpi_registe...keup_handler(9)

📦 version 7.3.1, in nixpkgs unstable

✨ acpi_registe...keup_handler(9) ✨

okay so bestie, welcome to the Kernel API Manual 💖 this one's literally called acpi_registe...keup_handler — yes the name is truncated like that in the header, no I didn't do it, that's just how it's printed, and yes it lives in section 9 of the manual. buckle up 🎀

🌸 NAME 🌸

acpi_register_wakeup_handler — register a wakeup handler 💅 that's the whole vibe, it registers a wakeup handler, iconic behaviour honestly

🦋 SYNOPSIS 🦋

int acpi_register_wakeup_handler (int wake_irq , bool (*wakeup)(void
*context) , void *context );

it returns an int, it takes three things, it's giving very straightforward main character energy ✨

🎀 ARGUMENTS 🎀

  • wake_irq — the IRQ through which the device may receive wakeups 🌈 like, this is the interrupt line your device is chilling on
  • wakeup — the wakeup-handler to call when the SCI has triggered a wakeup 🔥 note the signature: bool (*wakeup)(void *context), it's a function pointer, it's fancy
  • context — the context you pass to the handler when calling it 🫶 it gets handed straight back to your wakeup function, no cap

💜 DESCRIPTION 💜

so here's the tea ☕ drivers that may share an IRQ with the SCI can use this to register a handler. and that handler returns true when the device they are managing wants to trigger a wakeup 💀 literally the whole point.

that's it. that's the function. lowkey elegant ngl 🌸

⭐ SEE ALSO ⭐

kernel file ./drivers/acpi/wakeup.c is where this lives, and go peek at these besties too:

and that's the page!! 🧚 from ./drivers/acpi, dated October 2026, and the header/footer both say acpi_registe...keup_handler(9) because we love a consistent (if slightly truncated) brand 💅 stay hydrated, read your kernel source, periodt 👑💖

📦 where this page comes from