xe_force_wake_assert_held(9)

💅 xe_force_wake_assert_held — the vibe check for your forcewake domain

okay so bestie, welcome to the Kernel API Manual entry for xe_force_wake_assert_held, and honestly? it's giving "one job, and it does it." let me explain 🫶

---

✨ NAME ✨

xe_force_wake_assert_held — asserts domain is awake 💤➡️👑

---

🦋 SYNOPSIS 🦋

void xe_force_wake_assert_held (struct xe_force_wake *fw , enum
       xe_force_wake_domains domain );

that's it. that's the whole flex. no return value, no drama, just vibes and an assertion. periodt. 💅

---

🎀 ARGUMENTS 🎀

• fw — your xe_force_wake structure, the main character of this whole situation 👑
• domain — an xe_force_wake_domains value, and listen, it has to be apart from XE_FORCEWAKE_ALL. one domain only, no bundling, we don't do combo deals here 🙈

---

🌸 DESCRIPTION 🌸

so xe_force_wake_assert_held is literally designed to confirm that one particular forcewake domain is awake. that's the whole assignment. it checks a single domain's wakefulness, and it does not verify the wakefulness of multiple domains — not its job, not its problem, not today 😭

which brings us to the big rule: make sure the caller doesn't input multiple domains (XE_FORCEWAKE_ALL) as a parameter. like, fr fr, don't do it. this function is for one domain, bestie. give it one domain. it will slay. give it XE_FORCEWAKE_ALL and you're just setting yourself up 💀

⚠️ heads up: XE_FORCEWAKE_ALL is not a valid parameter here — the function is only built to assert a single domain, not a whole set of them. keep it singular, keep it cute. ✨

---

🔥 SEE ALSO 🔥

• the kernel file ./drivers/gpu/drm/xe/xe_force_wake.h — go read it, it's iconic 📖
• xe_force_wake_ref_has_domain(9) — the sibling function, also very much worth your time 🧚

---

🌈 a little sign-off 🌈

this page lives over in ./drivers/gpu/drm/xe, it's dated October 2026, and it's officially page xe_force_wake_assert_held(9) of the Kernel API Manual. ok that's the whole thing, love u, go assert some domains 💖✨🍓