xe_pm_runtime_resume(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ xe_pm_runtime_resume ✨ (that's the page, bestie β€” live from the Kernel API Manual πŸ’…)

okay so picture this: it's giving kernel-docs-but-make-it-cute. this is xe_pm_runtime_resume(9), and yes it's a real function in the Kernel API Manual, we're not making it up 🫢


🌸 NAME 🌸

xe_pm_runtime_resume β€” literally just Waking up from D3hot/D3Cold. that's the whole vibe. the device was napping in a deep power state and this is the glow-up moment where it comes back 😴➑️✨


πŸŽ€ SYNOPSIS πŸŽ€

int xe_pm_runtime_resume(struct xe_device *xe);

one function, one argument, returns an int. simple. iconic. no cap πŸ’…


πŸ’– ARGUMENTS πŸ’–

  • xe β€” the xe device instance. like, the device. your main character. the one you're waking up πŸ¦‹

⭐ DESCRIPTION ⭐

so what does it actually do? it wakes stuff up from D3hot/D3Cold, that's the whole thing, and then it tells you how it went:

  • returns 0 for success πŸŽ‰ (we love a zero, a zero is a win)
  • returns a negative error code otherwise 😭 (not a win, but at least it's honest)
fr fr that's the entire description β€” no hidden lore, no extra caveats, this one's a short king πŸ‘‘

🌈 SEE ALSO 🌈

okay this list is long and honestly kind of a flex, so buckle up bestie, we're going through all of it 🧚

yeah. twenty-three entries. the PM family is huge and every single one of them is invited to the group chat πŸ”₯


and that's the page!! sourced straight from ./drivers/gpu/drm/xe, dated October 2026 β€” so yeah, this manual page is from the future, slay, we don't question it πŸ’€πŸ‘‘ bye bestie, go wake up some hardware πŸ«ΆπŸ’–

πŸ“¦ where this page comes from