intel_gt_mcr_unicast_write(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… intel_gt_mcr_unicast_write(9) πŸ’…

okay so welcome to the Kernel API Manual page for intel_gt_mcr_unicast_write(9), bestie. This is the little function that writes one specific instance of an MCR register, and it is lowkey iconic for knowing exactly which group/instance it wants. ✨

πŸ’– NAME πŸ’–

intel_gt_mcr_unicast_write β€” write a specific instance of an MCR register. That’s the whole assignment: one register instance, unicast mode, no cap. πŸŽ€

✨ SYNOPSIS ✨

void intel_gt_mcr_unicast_write (struct intel_gt *gt , i915_mcr_reg_t
reg , u32 value , int group , int instance );

🌸 ARGUMENTS 🌸

  • gt β€” the GT structure. Bestie, this is the context object you’re handing over. 🫢
  • reg β€” the MCR register to write. The main character register, fr fr. πŸ‘‘
  • value β€” value to write. Yep, the actual value going in. πŸ’…
  • group β€” the MCR group. Gotta know your group. πŸŽ€
  • instance β€” the MCR instance. And gotta know your instance too. ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

Write an MCR register in unicast mode after steering toward a specific group/instance. That’s it β€” that’s the vibe. It knows exactly which group/instance it’s steering toward, then does the write. Slay. πŸ’–

πŸ”₯ CONTEXT πŸ”₯

Heads up: calls a function that takes and releases gt->mcr_lock. So yes, the lock is part of the situation β€” not you doing it manually, the called function handles the take-and-release. 🫑

🌈 SEE ALSO 🌈


mwah πŸ’‹ β€” source/version: ./drivers/gpu/drm/i915/gt; date: October 2026; page: intel_gt_mcr_unicast_write(9). πŸŽ€βœ¨

πŸ“¦ where this page comes from