radeon_ring_..._scratch_reg(9)

📦 version 7.3.1, in nixpkgs unstable

💅 radeon_ring_..._scratch_reg(9) — bestie's edition

okay so this is a page from the Kernel API Manual (radeon_ring_..._scratch_reg(9)), and honestly? it's a little one, but it's a cutie. tiny function, one job, does it well. let's get into it 🎀

✨ NAME ✨

radeon_ring_supports_scratch_reg — the vibe check that tells you whether a ring can write to scratch registers 🦋

🌸 SYNOPSIS 🌸

bool radeon_ring_supports_scratch_reg (struct radeon_device *rdev ,
struct radeon_ring *ring );

like, that's it. two args, one bool back. no drama, no cap 💅

🫶 ARGUMENTS 🫶

  • rdev — a radeon_device pointer. it's giving "the whole device, the main character" 👑
  • ring — a radeon_ring structure holding ring information. this one's the specific ring we're asking about, bestie 🔥

💖 DESCRIPTION 💖

so the whole point of this function: it checks if a specific ring supports writing to scratch registers — and yes, that's all asics, every single one, no exceptions, periodt ✨

it returns true if the ring supports writing to scratch regs, and false if not. literally that simple. no guessing, no vibes-based output, just a clean boolean 🧚

ngl this is the kind of function that just answers the question and goes back to its business. we love a low-drama icon 💜

🌈 SEE ALSO 🌈

the kernel file lives at ./drivers/gpu/drm/radeon/radeon_ring.c — that's the source, go say hi 🍓

and bestie, here's the whole ring crew, all in one place:

and that's the page!! 💀 written up in October 2026, living under ./drivers/gpu/drm/radeon, filed forever as radeon_ring_..._scratch_reg(9). mwah, go read the other ones too, ily 🫶💖✨

📦 where this page comes from