intel_gt_mc...ast_write_fw(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

ok so bestie, welcome to the Kernel API Manual</p> ✨ this page is all about intel_gt_mcr_multicast_write_fw β€” and what it does is, like, write a value to all instances of an MCR register. yep. all of them. every single one. no cap 🫢

(also yes the page title up top is all smushed like intel_gt_mc...ast_write_fw(9) β€” that's just the terminal doing its little truncation thing, the real name is the full one, iykyk πŸ’…)


✨ SYNOPSIS ✨

void intel_gt_mcr_multicast_write_fw (struct intel_gt *gt ,
i915_mcr_reg_t reg , u32 value );

like literally that's the whole signature, she's not complicated πŸ’–


πŸŽ€ ARGUMENTS πŸŽ€

  • gt β€” the GT structure 🌸 that's your graphics tile situation, she's the main character here
  • reg β€” the MCR register to write πŸ‘‘ the one you're targeting
  • value β€” value to write ✨ like, the actual number going in. that's it. that's the payload

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so 🫢 what this does is: it writes an MCR register in multicast mode to update all instances. all of them at once. one write, every instance, slay πŸ’…

⚠️ but hear me out β€” this function assumes the caller is already holding any necessary forcewake domains. it does not grab them for you. so if you haven't sorted your forcewake, that's on you bestie 😭

and if you're in a situation where forcewake should be obtained automatically, then don't use this one β€” use intel_gt_mcr_multicast_write instead. that's literally what she's for 🧚


πŸ”₯ CONTEXT πŸ”₯

the one rule, the vibe check you must pass:

The caller must hold gt->mcr_lock.

no lock, no write. periodt πŸ’€ like please don't skip this, the kernel will simply not be having a good time πŸ™ˆ


🌈 SEE ALSO 🌈

like the whole MCR friend group is linked here, go say hi πŸŽ€


and that's the whole page bestie, you ate πŸ’…βœ¨ this icon came out of ./drivers/gpu/drm/i915/gt, dated October 2026, and she's serving full Kernel API Manual energy πŸŒΈπŸ¦‹ go forth and multicast responsibly πŸ’œ

πŸ“¦ where this page comes from