cpu_cluster_pm_exit(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

cpu_cluster_pm_exit β€” CPU cluster low power exit notifier. This is the cpu_cluster_pm_exit(9) page from the Kernel API Manual, bestie πŸ’…βœ¨

✨ SYNOPSIS ✨

int cpu_cluster_pm_exit (void );

🌸 ARGUMENTS 🌸

  • void β€” no arguments, bestie. That's it. Nothing to pass, zero drama 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so picture this: all the cpus in a power domain are exiting form a low power state, and that state may have caused some blocks in the same power domain to reset. cpu_cluster_pm_exit is the notifier that tells all the listeners, β€œhey bestie, we're exiting form a low power state” β€” yes, form is literally how the source spells it, don't come for me πŸ˜­πŸ’€

Timing is the whole vibe here. You must call this after cpu_cluster_pm_enter has been called for the power domain, and before cpu_pm_exit has been called on any cpu in the power domain. No cap, order matters πŸ”₯πŸ‘‘

Who's listening? The notified drivers can include the VFP co-processor, the interrupt controller and its PM extensions, and local CPU timers context save/restore β€” and that save/restore stuff shouldn't be interrupted. Hence, it must be called with interrupts disabled. Periodt πŸ’…

Return conditions are the same as __raw_notifier_call_chain.

πŸŽ€ SEE ALSO πŸŽ€


Cute sign-off: that's the whole page, brought to you by the ./kernel source and dated October 2026 β€” cpu_cluster_pm_exit(9), slaying in the Kernel API Manual πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from