pvr_fw_mts_schedule(9)

💅 pvr_fw_mts_schedule(9) — like, the Kernel API Manual page, bestie

okay so this is pvr_fw_mts_schedule, straight out of the Kernel API Manual, and it's genuinely one of the shorter ones so we can absolutely devour this together 🫶

---

✨ NAME ✨

pvr_fw_mts_schedule — schedule work via an MTS kick 💫

---

🎀 SYNOPSIS 🎀

void pvr_fw_mts_schedule (struct pvr_device *pvr_dev , u32 val );

like, that's it. that's the whole signature. precious. no return value, we're just out here kicking things 🦋

---

🌸 ARGUMENTS 🌸

• pvr_dev — the target PowerVR device 👑 this is your main character, the device you're scheduling the work on.
• val — the kick mask 🔥 and listen, it should be a combination of ROGUE_CR_MTS_SCHEDULE_* — like, that's the vibe it's expecting, okay? a combo of those bad boys. ngl the manpage doesn't spell out which ones, it just says ROGUE_CR_MTS_SCHEDULE_*, so we're keeping it exactly that way. periodt 💅

---

🌈 SEE ALSO 🌈

Every single one of these, fr fr — no skipping, iykyk:

• Kernel file ./drivers/gpu/drm/imagination/pvr_fw.c
• pvr_fw_validate(9)
• pvr_fw_process(9)
• pvr_wait_for_fw_boot(9)
• pvr_fw_validate_init_device_info(9)
• pvr_fw_init(9)
• pvr_fw_fini(9)
• pvr_fw_structure_cleanup(9)
• pvr_fw_object_fw_map(9)
• pvr_fw_object_fw_unmap(9)
• pvr_fw_object_create(9)
• pvr_fw_object_create_and_map(9)
• pvr_fw_object_create_and_map_offset(9)
• pvr_fw_object_destroy(9)
• pvr_fw_object_get_fw_addr_offset(9)

bestie that's a lot of fw functions and every one of them is required reading. the manpage said so, not me 💀

---

and that's the whole page, iconically short, we ate and left no crumbs 🍓

so this lil manual page lives under ./drivers/gpu/drm/imagination, it's dated October 2026, and its whole identity is pvr_fw_mts_schedule(9) — mwah, see you at the next kick mask 🧚💜