dpm_complete(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– dpm_complete β€” from the Kernel API Manual, bestie πŸ’–

okay so like, welcome to the Kernel API Manual (section 9, we love a man-page moment), and today's main character is dpm_complete. she's short, she's sweet, she's lowkey doing a lot of work behind the scenes. let's get into it ✨


🌸 NAME 🌸

dpm_complete β€” Complete a PM transition for all non-sysdev devices.

like, all of them. every single non-sysdev device. she's thorough, she's that girl πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

void dpm_complete (pm_message_t state );

yup that's the whole thing. void return, one argument, no notes. iconic behavior honestly πŸŽ€


πŸ“ ARGUMENTS πŸ“

  • state β€” PM transition of the system being carried out. that's the vibe of the whole power-management moment you're in rn, she needs to know which one, k? 🫢

🌈 DESCRIPTION 🌈

okay so here's the tea: dpm_complete executes the ->complete callbacks for all devices whose PM status is not DPM_ON.

and why does that matter, you ask? because doing it this way (only the ones not already DPM_ON) allows new devices to be registered while this is happening. so the system can grow mid-transition. slay, honestly ✨

πŸ’€ no cap, that parenthetical is load-bearing β€” it's the whole reason for the status check. don't skip it.

🧚 SEE ALSO 🧚

like a group chat, but for kernel symbols. these are all the friends in the ./drivers/base/power/main.c orbit β€” go say hi πŸ‘‘

fr fr that's the whole roster, no cap, didn't skip a single one πŸ˜­πŸ’œ


and that's the page!! brought to you by ./drivers/base/power, dated October 2026, and obviously the icon herself, dpm_complete(9). go forth and complete those PM transitions, bestie 🌸🫢✨

πŸ“¦ where this page comes from