STRUCT PVR_FW_MEM(9)

👑 NAME 👑

struct pvr_fw_mem — the FW memory allocation situation, and bestie, it's a whole vibe ✨

So like, this is the struct that holds all the firmware memory allocations. Every pointer, every size, every object — it's all living in here. Periodt. 💅

---

🦋 SYNOPSIS 🦋

struct pvr_fw_mem {
    struct pvr_fw_object *code_obj;
    struct pvr_fw_object *data_obj;
    struct pvr_fw_object *core_code_obj;
    struct pvr_fw_object *core_data_obj;
    u8 *code;
    u8 *data;
    u8 *core_code;
    u8 *core_data;
    u32 code_alloc_size;
    u32 data_alloc_size;
    u32 core_code_alloc_size;
    u32 core_data_alloc_size;
    struct pvr_fw_object *fwif_connection_ctl_obj;
    struct pvr_fw_object *osinit_obj;
    struct pvr_fw_object *sysinit_obj;
    struct pvr_fw_object *osdata_obj;
    struct pvr_fw_object *hwrinfobuf_obj;
    struct pvr_fw_object *sysdata_obj;
    struct pvr_fw_object *power_sync_obj;
    struct pvr_fw_object *fault_page_obj;
    struct pvr_fw_object *gpu_util_fwcb_obj;
    struct pvr_fw_object *runtime_cfg_obj;
    struct pvr_fw_object *mmucache_sync_obj;
};

Like, look at her. She's got range. 🌈

---

🎀 Members 🎀

Okay so let's go through the whole cast, main-character by main-character 💖

🌸 The firmware sections (code & data) 🌸

• code_obj — the object that represents firmware code, fr fr.
• data_obj — the object that represents firmware data, no cap.
• core_code_obj — object representing firmware core code. Lowkey might be NULL if the firmware doesn't contain this section 👀
• core_data_obj — object representing firmware core data. Also may be NULL if the firmware doesn't contain this section. Not every firmware comes with the full set, iykyk 🫶
• code — the driver-side copy of firmware code. Like, the driver keeps its own lil duplicate 💅
• data — driver-side copy of firmware data.
• core_code — driver-side copy of firmware core code. May be NULL if the firmware doesn't contain this section 🙈
• core_data — driver-side copy of firmware core data. May be NULL if the firmware doesn't contain this section 🙈

✨ The allocation sizes ✨

• code_alloc_size — the allocation size of the firmware code section. Numbers, bestie 🔢
• data_alloc_size — allocation size of the firmware data section.
• core_code_alloc_size — allocation size of the firmware core code section.
• core_data_alloc_size — allocation size of the firmware core data section.

🧚 The FWIF / FW structure objects 🧚

• fwif_connection_ctl_obj — object representing the FWIF connection control structure. That's a lot of words but it ate 💅
• osinit_obj — object representing the FW OSINIT structure.
• sysinit_obj — object representing the FW SYSINIT structure.
• osdata_obj — object representing the FW OSDATA structure.
• hwrinfobuf_obj — object representing the FW hwrinfobuf structure.
• sysdata_obj — object representing the FW SYSDATA structure.

🔥 The rest of the cast 🔥

• power_sync_obj — object representing power sync state. Keeping the power in sync, iconic behaviour ⚡
• fault_page_obj — object representing the FW fault page. If something goes wrong, this is where it's at 😭
• gpu_util_fwcb_obj — object representing the FW GPU utilisation control structure. Utilisation! Control! Structure! 👑
• runtime_cfg_obj — object representing the FW runtime config structure.
• mmucache_sync_obj — object used as the sync parameter in an MMU cache operation. Very specific, very niche, we love her for it 🍓

---

⭐ SEE ALSO ⭐

Go read these next, bestie, they're literally linked in the kernel file ./drivers/gpu/drm/imagination/pvr_fw.h 🥰

• struct pvr_fw_object(9)
• struct pvr_fw_defs(9)
• pvr_fw_object_get_dma_addr(9)

---

Ngl the whole thing lives in ./drivers/gpu/drm/imagination/pvr_fw.h — that's the kernel file, the source of truth, the moment 💯

Okay that's the whole page, you're welcome, now go read some kernel source 🫶

Kernel API Manual ✨ struct pvr_fw_mem(9) ✨ from ./drivers/gpu/drm/imagination ✨ October 2026 ✨ mwah, slay, bye! 💅🎀🦋