vce_v1_0_is_idle(9)

💖 vce_v1_0_is_idle — the vibe check for VCE1 💖

Ok bestie, so this one lives in the Kernel API Manual and it's literally called vce_v1_0_is_idle. She's a kernel function, she's bool, and she's here to tell you whether the VCE1 IP block is chilling or grinding. Periodt.

---

✨ SYNOPSIS ✨

bool vce_v1_0_is_idle (struct amdgpu_ip_block *ip_block );

Yeah, that's the whole signature — one argument, one bool return, zero drama. 🎀

---

🌸 ARGUMENTS 🌸

• ip_block — an amdgpu_ip_block pointer, that's it, that's the whole ✨situation✨. Hand her the IP block and she'll go check on it.

---

🦋 DESCRIPTION 🦋

So here's the tea 🍵: she checks whether VCE is busy according to VCE_STATUS. That's like the main character check, the real source of truth.

But wait, there's more — she also checks whether the SRBM thinks VCE is busy. And ngl, that second check is giving ✨suspicious✨, because SRBM_STATUS.VCE_BUSY seems to be bogus 😭. Like, it appears to mirror the VCE_STATUS.VCPU_REPORT_FW_LOADED bit, which is... not the same thing, bestie. So that whole SRBM vibe check is questionable, iykyk. 💀

Fr fr though: the SRBM side is noted in the docs as seeming bogus because it looks like it mirrors VCE_STATUS.VCPU_REPORT_FW_LOADED. Keep that in mind, don't @ me.

---

🫶 SEE ALSO 🫶

The kernel file itself, the icon, the queen 👑:

• ./drivers/gpu/drm/amd/amdgpu/vce_v1_0.c

And her whole friend group — the rest of the vce_v1_0 squad, no cap:

• vce_v1_0_ring_get_rptr(9)
• vce_v1_0_ring_get_wptr(9)
• vce_v1_0_ring_set_wptr(9)
• vce_v1_0_load_fw(9)
• vce_v1_0_start(9)
• vce_v1_0_ensure_vcpu_bo_32bit_addr(9)
• vce_v1_0_hw_init(9)

---

🌈 THE SIGN-OFF 🌈

This lil page lives under ./drivers/gpu/drm/amd/amdgpu, dated October 2026 💅 — go off, calendar. And that's the whole Kernel API Manual entry for vce_v1_0_is_idle(9). Slay, stay idle, drink water 🍓🧚💜