intel_gt_mcr_read_any(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… intel_gt_mcr_read_any β€” from the Kernel API Manual, bestie

okay so picture this: you're deep in the i915 driver and you just need one value out of an MCR register. not a whole song and dance, just one read. that's this function. it's literally the "just grab me a value" girlypop of the GT MCR world ✨


🌸 NAME 🌸

intel_gt_mcr_read_any β€” reads one instance of an MCR register

like, one instance. singular. she's not doing a whole multicast situation, she's picking a valid one and going with it. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

u32 intel_gt_mcr_read_any (struct intel_gt *gt , i915_mcr_reg_t reg );

πŸ“ ARGUMENTS πŸ“

  • gt β€” GT structure. the whole graphics tile situation, the context of where we're reading from πŸ’–
  • reg β€” register to read. the actual MCR register you're curious about πŸ‘‘

✨ DESCRIPTION ✨

Reads a GT MCR register. simple enough, right? but here's the tea: the read gets steered to a non-terminated instance β€” meaning an instance that isn't fused off and isn't powered down by power gating. so she sniffs around and picks one that's actually alive to answer. no cap. πŸ”₯

Returns the value from a non-terminated instance of reg. that's the whole vibe: you give her a register, she gives you back a real number from a real, living instance. 🫢


⭐ CONTEXT ⭐

Calls a function that takes and releases gt->mcr_lock.

so like, heads up bestie β€” the lock gets grabbed and dropped inside this call. if you're already holding gt->mcr_lock yourself, that's a you problem and you should look at the non-locking variants. iykyk πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/gpu/drm/i915/gt/intel_gt_mcr.c


okay that's the whole page, mwah πŸ’‹ this one lives in ./drivers/gpu/drm/i915/gt and the version tag on it says October 2026 β€” go off, calendar icon πŸ—“οΈβœ¨

πŸ“¦ where this page comes from