intel_uncore_forcewake_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… intel_uncore_forcewake_get(9) πŸ’…

ok so this is a page straight out of the Kernel API Manual, bestie β€” we're talking kernel-level lore today, and honestly? it's giving main character energy. let's get into it 🫢


✨ NAME ✨

intel_uncore_forcewake_get β€” grab forcewake domain references πŸ”₯


🌸 SYNOPSIS 🌸

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

like, that's the whole signature. void return, two args, no games. πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • uncore β€” the intel_uncore structure. yes queen, that's the one. πŸ¦‹
  • fw_domains β€” the forcewake domains you're grabbing a reference on. pick your faves (or all of them, we'll get there). ✨

πŸ’– DESCRIPTION πŸ’–

okay so here's the tea β˜• β€” this function is how you get GT's forcewake domain references. slay.

and like, normally? normal register access handles the forcewake domains automatically. no cap, it just does it for you. πŸ™ˆ

BUT β€” and this is the important part, bestie β€” if some sequence requires the GT to not power down a particular forcewake domain, then you should call this function at the beginning of that sequence. periodt. and then, subsequently, you drop that reference by making a symmetric call to intel_unforce_forcewake_put. you gotta match them up, it's giving balance. βš–οΈ

usually the caller wants all the domains kept awake, so in that case fw_domains would just be FORCEWAKE_ALL. all of them. every single one. icon behavior. πŸ‘‘


πŸ¦‹ SEE ALSO πŸ¦‹

the kernel file lives right here, go look:

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

and the whole friend group πŸ’œ:


okay that's the page!! πŸ’« this one came from ./drivers/gpu/drm/i915, dated October 2026, and it's filed under intel_uncore_forcewake_get(9) in case you need to find it again. mwah, go keep those domains awake bestie πŸ˜­πŸ’–πŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from