acpi_subsys_suspend(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ acpi_subsys_suspend(9) ✨

okay so real talk, bestie β€” you're reading a page from the Kernel API Manual, and it's all about acpi_subsys_suspend. yes that's a mouthful, no i will not be pronouncing it out loud πŸ’…


🌸 NAME 🌸

acpi_subsys_suspend β€” literally just runs the device driver's suspend callback. that's the whole vibe. no cap. 🫢


πŸŽ€ SYNOPSIS πŸŽ€

int acpi_subsys_suspend (struct device *dev );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the device you're handling. that's it, that's the arg. give it a device, she'll do her thing πŸ’–

⭐ DESCRIPTION ⭐

so here's the tea β˜• β€” this function follows PCI and resumes devices from runtime suspend before running their system suspend callbacks.

BUT (and this is the important but, don't skip it πŸ™ˆ) there's an exception, and there are two conditions that both have to hold for it:

  • the driver can cope with runtime-suspended devices during system suspend, and
  • there are no ACPI-specific reasons for resuming them.

if both of those are true? then she doesn't do the resume-first thing. if either one fails β€” or honestly if you're not sure β€” resume happens first. periodt. πŸ”₯


πŸ‘‘ SEE ALSO πŸ‘‘

the whole squad lives in the kernel file ./drivers/acpi/device_pm.c and honestly, it's giving extended family reunion. here's everybody:

like i said. reunion. iconic behavior, truly 🌈


and that's the whole page, bestie!! πŸŽ€ this gem comes to you from ./drivers/acpi, dated October 2026, and it goes by acpi_subsys_suspend(9). go take a nap now, you've earned it πŸ˜­πŸ’œ

πŸ“¦ where this page comes from