pvr_cccb_send_kccb_kick(9)

✨ pvr_cccb_send_kccb_kick(9) ✨

Okay bestie, welcome to the Kernel API Manual page for pvr_cccb_send_kccb_kick(9) — it’s all about sending a KCCB kick to trigger command processing, and honestly? Iconic kernel behavior 💅. Let’s get into it.

---

🌸 NAME 🌸

pvr_cccb_send_kccb_kick — send KCCB kick to trigger command processing.

---

✨ SYNOPSIS ✨

void pvr_cccb_send_kccb_kick (struct pvr_device *pvr_dev , struct pvr_cccb *pvr_cccb , u32 cctx_fw_addr , struct pvr_hwrt_data *hwrt );

It’s a void function, so there’s no return value to catch — no cap.

---

🎀 ARGUMENTS 🎀

Here’s the whole cast, bestie:

• pvr_dev — Device pointer. The whole device vibe.
• pvr_cccb — Pointer to CCCB to process. This is the star of the show.
• cctx_fw_addr — FW virtual address for context owning this Client CCB.
• hwrt — HWRT data set associated with this kick. May be NULL.

---

💅 DESCRIPTION 💅

The mandatory pregame is this: call pvr_kccb_reserve_slot, and if this function didn’t return NULL, wait for the returned fence to signal. Only after that should you call pvr_cccb_send_kccb_kick.

⚠️ Do not skip the pvr_kccb_reserve_slot + fence step before calling pvr_cccb_send_kccb_kick. That’s the rule, and the rule is giving very serious.

---

🦋 SEE ALSO 🦋

Kernel file: ./drivers/gpu/drm/imagination/pvr_cccb.c.

Also peep pvr_cccb_init(9), pvr_cccb_fini(9), pvr_cccb_cmdseq_fits(9), and pvr_cccb_write_command_with_header(9). Iykyk 💖.

---

💖 Cute little sign-off: source/version is ./drivers/gpu/drm/imagination, dated October 2026, for pvr_cccb_send_kccb_kick(9). Byeee 🫶