intel_uncore..._get__locked(9)

💅 intel_uncore..._get__locked(9) 💅

okay so bestie, welcome to the Kernel API Manual — yes the actual manual, page intel_uncore..._get__locked(9), and no I did not stutter, that name really is that long, she's just dramatic like that 🎀

✨ NAME ✨

intel_uncore_forcewake_get__locked — grab forcewake domain references 🫶

🌸 SYNOPSIS 🌸

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

like, look at her. a whole function signature. she ate 💅

🦋 ARGUMENTS 🦋

• uncore — the intel_uncore structure, your main character struct ngl 💖
• fw_domains — the forcewake domains you wanna get a reference on, slay ✨

👑 DESCRIPTION 👑

ok so lowkey the real tea is in intel_uncore_forcewake_get — go read that one, fr fr. This variant is the spicy one: it places the onus on you, the caller, to explicitly handle the dev_priv->uncore.lock spinlock. yes. you. personally. no cap 🙈

⚠️ bestie please actually handle that spinlock, the whole point of the __locked suffix is that the locking is your job now. it's giving main character energy and main character responsibility 😭

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/i915/intel_uncore.c 🍓
• intel_uncore_forcewake_get(9)
• intel_uncore_forcewake_user_get(9)
• intel_uncore_forcewake_user_put(9)
• intel_uncore_forcewake_put(9)
• intel_uncore_forcewake_flush(9)
• intel_uncore_forcewake_put__locked(9)
• __intel_wait_for_register_fw(9)
• __intel_wait_for_register(9)
• intel_uncore_forcewake_for_reg(9)

like, the whole friend group showed up. iykyk 💀

and that's the whole page bestie!! 🌟 this lil masterpiece lives over in ./drivers/gpu/drm/i915, dated October 2026, and it goes by intel_uncore..._get__locked(9) — mwah, iconic, no notes 💜🧚‍♀️