uvd_v6_0_hw_fini(9)
β¨ NAME β¨
uvd_v6_0_hw_fini β stop the hardware block π
okay so this page is from the Kernel API Manual, bestie, and this function is uvd_v6_0_hw_fini. Its whole vibe is stopping the hardware block. Slay. π
πΈ SYNOPSIS πΈ
int uvd_v6_0_hw_fini (struct amdgpu_ip_block *ip_block );
That's the exact signature, no cap β an int return and a struct amdgpu_ip_block *ip_block argument. π«Ά
π ARGUMENTS π
ip_blockβ pointer to theamdgpu_ip_blockfor this hw instance. It's giving βthis specific hardware block's little pointer,β and yes, you need it. π
π¦ DESCRIPTION π¦
Stop the UVD block, and mark the ring as not ready any more. Literally that's the whole thing: the UVD block gets stopped, and the ring is marked as not ready any more. Periodt. πβ¨
π SEE ALSO π
Kernel file: ./drivers/gpu/drm/amd/amdgpu/uvd_v6_0.c
go check these besties too, iykyk:
uvd_v6_0_enc_support(9)uvd_v6_0_ring_get_rptr(9)uvd_v6_0_enc_ring_get_rptr(9)uvd_v6_0_ring_get_wptr(9)uvd_v6_0_enc_ring_get_wptr(9)uvd_v6_0_ring_set_wptr(9)uvd_v6_0_enc_ring_set_wptr(9)uvd_v6_0_enc_ring_test_ring(9)uvd_v6_0_enc_get_create_msg(9)uvd_v6_0_enc_get_destroy_msg(9)uvd_v6_0_enc_ring_test_ib(9)uvd_v6_0_hw_init(9)uvd_v6_0_mc_resume(9)uvd_v6_0_start(9)uvd_v6_0_stop(9)uvd_v6_0_ring_emit_fence(9)uvd_v6_0_enc_ring_emit_fence(9)uvd_v6_0_ring_emit_hdp_flush(9)uvd_v6_0_ring_test_ring(9)uvd_v6_0_ring_emit_ib(9)uvd_v6_0_enc_ring_emit_ib(9)
mwah π this uvd_v6_0_hw_fini(9) cutie comes from the ./drivers/gpu/drm/amd/amdgpu source/version corner and is dated October 2026. byeee, go stop that UVD block responsibly π«Άβ¨
π¦ 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