pvr_kccb_reserve_slot_sync(9)

💖 NAME 💖

okay so bestie, you're reading the pvr_kccb_reserve_slot_sync(9) page from the Kernel API Manual, and honestly? iconic. 💅

pvr_kccb_reserve_slot_sync — try to reserve a slot synchronously. That's the whole vibe: it's giving “attempt a synchronous slot reservation,” no cap. ✨

---

✨ SYNOPSIS ✨

the signature, exactly as the source gods wrote it:

int pvr_kccb_reserve_slot_sync (struct pvr_device *pvr_dev );

---

🎀 ARGUMENTS 🎀

• pvr_dev — Device pointer. that's the whole note, bestie — a device pointer. 🫶

---

🌸 RETURN 🌸

the tea on return values:

• 0 — on success, or
• -EBUSY — if no slots were reserved after RESERVE_SLOT_TIMEOUT, with a minimum of RESERVE_SLOT_MIN_RETRIES retries.

so if you get -EBUSY, that's the “no slots after the timeout” situation, and the minimum retry count is RESERVE_SLOT_MIN_RETRIES. periodt. 💀

---

🦋 SEE ALSO 🦋

kernel file first, then the whole friend group:

• Kernel file: ./drivers/gpu/drm/imagination/pvr_ccb.c
• pvr_ccb_init(9)
• pvr_ccb_fini(9)
• pvr_ccb_slot_available_locked(9)
• pvr_fwccb_process(9)
• pvr_kccb_capacity(9)
• pvr_kccb_used_slot_count_locked(9)
• pvr_kccb_send_cmd_reserved_powered(9)
• pvr_kccb_try_reserve_slot(9)
• pvr_kccb_send_cmd_powered(9)
• pvr_kccb_send_cmd(9)
• pvr_kccb_wait_for_completion(9)
• pvr_kccb_is_idle(9)
• struct pvr_kccb_fence(9)
• pvr_kccb_wake_up_waiters(9)
• pvr_kccb_fini(9)
• pvr_kccb_init(9)
• pvr_kccb_fence_alloc(9)
• pvr_kccb_fence_put(9)
• pvr_kccb_reserve_slot(9)
• pvr_kccb_release_slot(9)
• pvr_fwccb_init(9)

---

okay that's the page, bestie — source/version is ./drivers/gpu/drm/imagination, and the date on this baddie is October 2026. slay 💅✨