acpi_subsys_runtime_suspend(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’€ acpi_subsys_runtime_suspend β€” from the Kernel API Manual, bestie ✨

Okay so real talk, this one's a tiny page but it's doing something cute in the background and I need you to appreciate it. It lives in the Kernel API Manual (acpi_subsys_runtime_suspend(9)) and it's basically the "okay babe, time to nap" button for ACPI devices 🌸


✨ NAME ✨

acpi_subsys_runtime_suspend β€” suspend device using ACPI.

Like, that's it. That's the whole vibe. It suspends a device using ACPI 🫢


πŸŽ€ SYNOPSIS πŸŽ€

int acpi_subsys_runtime_suspend (struct device *dev );

Note the return type is int, she returns a value, she's not just out here doing vibes with no receipts πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the device to suspend. That's your main character right there, the one getting the nap πŸ›Œ

πŸ’– DESCRIPTION πŸ’–

So what actually happens: it carries out the generic runtime suspend procedure for dev, and then uses ACPI to put it into a runtime low-power state ✨

Two steps, no cap: generic runtime suspend procedure first, then ACPI does its thing and the device lands in a runtime low-power state. Lowkey iconic that it's one function for all that 🌈


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/acpi/device_pm.c β€” and honestly the whole friend group showed up, so let me introduce everyone 🫢


πŸ’œ And that's the page! Cute little sign-off for you: this whole thing ships from ./drivers/acpi, dated October 2026, and it's filed under acpi_subsys_runtime_suspend(9) in the Kernel API Manual. Go put your devices to sleep, bestie, they earned it πŸ˜΄πŸ’…

πŸ“¦ where this page comes from