intel_uncore..._put__locked(9)

💅 NAME 💅

intel_uncore_forcewake_put__locked — bestie, this one releases your forcewake domain references ✨ (and yes the double underscore is part of the vibe, don't @ me)

So this whole page lives in the Kernel API Manual, which is exactly as iconic as it sounds 🎀

---

🌸 SYNOPSIS 🌸

void intel_uncore_forcewake_put__locked (struct intel_uncore *uncore ,
enum forcewake_domains fw_domains );

🦋 ARGUMENTS 🦋

• uncore — the intel_uncore structure, aka the main character of this whole function 🫶
• fw_domains — the forcewake domains you're putting references to, iykyk

---

✨ DESCRIPTION ✨

Okay so first things first, go read intel_uncore_forcewake_put — that's the sibling function, the blueprint, the lore 💖

This variant is the locked one, and it's giving "you're on your own, bestie." It places the onus on the caller to explicitly handle the dev_priv->uncore.lock spinlock 🔒

Not me about to say this again but fr fr: YOU, the caller, must handle dev_priv->uncore.lock yourself. This function will not do it for you. No cap, no hand-holding, no safety net 💀

---

👑 SEE ALSO 👑

The kernel file where all of this lives:

• ./drivers/gpu/drm/i915/intel_uncore.c

And the whole friend group of related functions, all so valid:

• intel_uncore_forcewake_get(9)
• intel_uncore_forcewake_user_get(9)
• intel_uncore_forcewake_user_put(9)
• intel_uncore_forcewake_get__locked(9)
• intel_uncore_forcewake_put(9)
• intel_uncore_forcewake_flush(9)
• __intel_wait_for_register_fw(9)
• __intel_wait_for_register(9)
• intel_uncore_forcewake_for_reg(9)

---

okay that's the whole page bestie, you ate that 💅✨

Dropping the credits real quick 🎬 — this one's from ./drivers/gpu/drm/i915, dated October 2026, and it's the intel_uncore..._put__locked(9) page. Go forth and handle your spinlocks responsibly 🫶💖