acpi_bus_notify(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– acpi_bus_notify(9) β€” like, the Kernel API Manual entry, bestie πŸ’–

okay so we're doing a manpage from the Kernel API Manual, section 9, and honestly? this one's a little diva β€” tiny page, big "i only do one thing" energy. but that one thing is lowkey important so let's get into it 🫢


✨ NAME ✨

acpi_bus_notify β€” the global system-level (0x00-0x7F) notifications handler πŸ’…

like, that's the whole flex. it's the handler for that range. no cap.


🌸 SYNOPSIS 🌸

void acpi_bus_notify (acpi_handle handle , u32 type , void *data );

yes the spacing in there is a little crunchy, that's just how the manpage wrote it, leave her alone 😭


πŸ¦‹ ARGUMENTS πŸ¦‹

  • handle β€” the target ACPI object. this is the thing we're talking about, the main character of the call ✨
  • type β€” the notification type. tells you what kind of notification is happening.
  • data β€” ignored. periodt. it's there, it's in the signature, we do not look at it. πŸ’€

πŸŽ€ DESCRIPTION πŸŽ€

okay so here's the tea: this handler only handles notifications related to device hotplug. that's it. that's the whole scope. if you were hoping it does more β€” nope, not her job πŸ™ˆ


πŸ’œ SEE ALSO πŸ’œ

that's a whole friend group right there honestly, they all hang out in the same part of the kernel 🌈


reminder bestie: data is ignored. don't build your whole personality around passing something useful in there, she will not be reading it 😌

and that's the page! pookie this came straight out of ./drivers/acpi, October 2026 edition, delivered to you by the Kernel API Manual herself. slay, stay hydrated, and go read your notify handlers πŸ’…πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from