amdgpu_mm_wreg_mmio_rlc(9)

💅 amdgpu_mm_wreg_mmio_rlc — like, the register writer, bestie

okay so real quick: this is from the Kernel API Manual (the section 9 girlies know what's up ✨), and we're talking about amdgpu_mm_wreg_mmio_rlc. Yes the name is a whole mouthful, no I will not be shortening it, it's iconic as is. 🎀

---

✨ NAME ✨

amdgpu_mm_wreg_mmio_rlc — writes a register, and it's giving options: either you go the direct/indirect mmio route, or you take the RLC path if you're in range. versatile queen 💅

---

🌸 SYNOPSIS 🌸

void amdgpu_mm_wreg_mmio_rlc (struct amdgpu_device *adev , uint32_t reg
, uint32_t v , uint32_t xcc_id );

---

🦋 ARGUMENTS 🦋

• adev — an amdgpu_device pointer, aka the main character of this whole operation 👑
• reg — the mmio/rlc register you're writing to, bestie
• v — the value you wanna write, the actual content of the vibe
• xcc_id — the xcc accelerated compute core id (yes that's a real thing, and yes you need it 🫶)

---

💜 DESCRIPTION 💜

okay so the tea: this function is only invoked for the debugfs register access. that's it, that's the whole scope, no cap. it's a debugfs-only girlie, and honestly? respect. 💀

---

🌈 SEE ALSO 🌈

the whole friend group, fr fr — go check the kernel file ./drivers/gpu/drm/amd/amdgpu/amdgpu_reg_access.c and also:

• amdgpu_device_rreg(9)
• amdgpu_mm_rreg8(9)
• amdgpu_device_xcc_rreg(9)
• amdgpu_mm_wreg8(9)
• amdgpu_device_wreg(9)
• amdgpu_device_xcc_wreg(9)
• amdgpu_device_indirect_rreg(9)
• amdgpu_device_indirect_rreg64(9)
• amdgpu_device_indirect_wreg(9)
• amdgpu_device_indirect_wreg64(9)

---

and that's the page, bestie 🍓 huge shoutout to the source at ./drivers/gpu/drm/amd/amdgpu, dated October 2026 — literally slayed, mwah 💖🧚‍♀️