dpm_suspend_noirq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŒ™ dpm_suspend_noirq(9) β€” Kernel API Manual, bestie edition

okay so you're reading the dpm_suspend_noirq(9) page and honestly? it's a short one, but it's doing something kind of iconic in the power-management pipeline. let's get into it πŸ’…


✨ NAME ✨

dpm_suspend_noirq β€” Execute "noirq suspend" callbacks for all devices.

like, all of them. the whole squad. 🫢


🌸 SYNOPSIS 🌸

int dpm_suspend_noirq (pm_message_t state );

πŸŽ€ ARGUMENTS πŸŽ€

  • state β€” the PM transition of the system being carried out. like, which flavour of sleep we're doing rn. that's the vibe check for the whole operation ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

bestie. listen. what this does is two things, and they're both lowkey the whole point:

  • it prevents device drivers' interrupt handlers from being called (yes, blocks them, no interruptions allowed, we're in our quiet era πŸ™ˆ)
  • and it invokes the "noirq" suspend callbacks for all non-sysdev devices.

so basically: hush the interrupt handlers, then run the noirq suspend callbacks across every non-sysdev device. periodt. 🌈

ngl the double quotes around "noirq" in the original are doing main character energy β€” they're telling you it's a named callback category, not just a descriptive word. keep them exactly like that πŸ’–

πŸ‘‘ SEE ALSO πŸ‘‘

the kernel file ./drivers/base/power/main.c is where the magic lives, and the whole friend group shows up here β€” go read these too, iykyk:


and that's the whole page, babe πŸ’œ source/version squad represent: this lives under ./drivers/base/power, it's dated October 2026, and the page itself is dpm_suspend_noirq(9) β€” go off, kernel docs, you ate πŸ“βœ¨

πŸ“¦ where this page comes from