pvr_fw_object_fw_map(9)

💅 pvr_fw_object_fw_map(9)

okay bestie, welcome to the pvr_fw_object_fw_map(9) page — it lives in the Kernel API Manual and it's literally the glow-up that gets a FW object a spot in firmware address space ✨

---

🌸 NAME 🌸

pvr_fw_object_fw_map — map a FW object in firmware address space 🗺️💖

---

🎀 SYNOPSIS 🎀

int pvr_fw_object_fw_map (struct pvr_device *pvr_dev , struct
       pvr_fw_object *fw_obj , u64 dev_addr );

---

🦋 ARGUMENTS 🦋

• pvr_dev — the device pointer, your main character 🫶
• fw_obj — the FW object you're trying to map, slay 💅
• dev_addr — the address in device space you actually want, if you need a specific one. If you don't care? Just pass 0 and let it vibe 🍓

---

🔥 RETURN 🔥

• 0 on success — periodt, we ate 💀✨
• -EINVAL if fw_obj is already mapped but has no references — yeah, awkward 🙈
• any error returned by DRM 😭

---

👑 SEE ALSO 👑

Kernel file ./drivers/gpu/drm/imagination/pvr_fw.c plus the whole friend group: 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_mts_schedule(9), pvr_fw_structure_cleanup(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) 🌈💜

---

and that's the whole page, no cap — brought to you by ./drivers/gpu/drm/imagination, dated October 2026, signing off as pvr_fw_object_fw_map(9) 🧚‍♀️⭐💖