jpeg_v5_0_2...ing_get_wptr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’« jpeg_v5_0_2_dec_ring_get_wptr πŸ’«

okay so welcome to the Kernel API Manual, bestie β€” today's main character is jpeg_v5_0_2_dec_ring_get_wptr, and honestly? she's short, she's sweet, she's giving "one job and she does it." Let's get into it πŸŽ€


✨ NAME ✨

jpeg_v5_0_2_dec_ring_get_wptr β€” get write pointer πŸ–ŠοΈβœ¨

Like, that's it. That's the whole vibe. She gets the write pointer. Iconic behavior, no notes.


🌸 SYNOPSIS 🌸

uint64_t jpeg_v5_0_2_dec_ring_get_wptr (struct amdgpu_ring *ring );

ngl the signature is literally one line and it returns a uint64_t. Slay. πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • ring β€” an amdgpu_ring pointer 🫢 that's the whole argument list, bestie, she travels light.

πŸ‘‘ DESCRIPTION πŸ‘‘

Returns the current hardware write pointer. periodt. πŸ’€

That's the entire description, and honestly we love a function that knows exactly what it is. No lore, no backstory, just the current hardware write pointer πŸ”₯


🧚 SEE ALSO 🧚

the whole friend group is here tbh β€” get_rptr is her sister, set_wptr is the one who actually sets things, and the rest are the init/fini/suspend/resume/start/stop girlies holding it all together πŸ’–


πŸ’‘ friendly reminder: everything above came straight from ./drivers/gpu/drm/amd/amdgpu, dated October 2026, in the Kernel API Manual. mwah πŸ’‹ go read the source, iykyk πŸ¦‹
πŸ“¦ where this page comes from