uvd_v5_0_mc_resume(9)
π uvd_v5_0_mc_resume β¨
Okay so bestie, welcome to the uvd_v5_0_mc_resume(9) page from the Kernel API Manual β yes that's the manual name, we're fancy here π β and honestly? This one's a little cutie. Short, sweet, and it's giving "just tell the memory controller where stuff lives" energy. Let's get into it π«Ά
πΈ NAME πΈ
uvd_v5_0_mc_resume β memory controller programming, periodt π
β¨ SYNOPSIS β¨
void uvd_v5_0_mc_resume (struct amdgpu_device *adev );
No cap, that's the whole signature. No return value, just vibes and one pointer π
π¦ ARGUMENTS π¦
adevβ anamdgpu_devicepointer, aka the main character of this whole situation π
π DESCRIPTION π
So what does it actually do? It lets the UVD memory controller know its offsets. That's it. That's the whole description. Lowkey iconic that they said it in one line and dipped π
Think of it as the moment the UVD memory controller gets its little map and finally knows where everything is β very "here's your address, bestie, go slay" energy β¨
π SEE ALSO π
The kernel file this whole thing lives in, fr fr:
./drivers/gpu/drm/amd/amdgpu/uvd_v5_0.c
And the whole friend group of related functions β go say hi to all of them π
uvd_v5_0_ring_get_rptr(9)uvd_v5_0_ring_get_wptr(9)uvd_v5_0_ring_set_wptr(9)uvd_v5_0_hw_init(9)uvd_v5_0_hw_fini(9)uvd_v5_0_start(9)uvd_v5_0_stop(9)uvd_v5_0_ring_emit_fence(9)uvd_v5_0_ring_test_ring(9)uvd_v5_0_ring_emit_ib(9)
π Reminder bestie: this page is terse on purpose. Don't go inventing behaviour that isn't written here β if it's not in the description, it's not in the description. Stay delulu only about your code, not the docs π
β And that's a wrap! This little gem comes to you from ./drivers/gpu/drm/amd/amdgpu, dated October 2026, and it lives at uvd_v5_0_mc_resume(9). Stan the kernel docs, mwah ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms