STRUCT IVPU_IPC_HDR(9)

✨ struct ivpu_ipc_hdr(9) ✨

okay so bestie, buckle up 💖 this one's from the Kernel API Manual and it's literally all about struct ivpu_ipc_hdr — the IPC message header structure, exchanged with the VPU device firmware. yes, that's the whole vibe: it's the little header that rides along with every message the driver and the VPU firmware pass back and forth 🫶

---

🌸 NAME 🌸

struct ivpu_ipc_hdr — the IPC message header structure, exchanged with the VPU device firmware. that's it, that's the queen 👑

---

🎀 SYNOPSIS 🎀

struct ivpu_ipc_hdr {
    u32 data_addr;
    u32 data_size;
    u16 channel;
    u8 src_node;
    u8 dst_node;
    u8 status;
 };

look at her. six fields, immaculate energy, no notes 💅 (and yes, character-for-character, that's exactly how she's declared — don't come for me)

---

🦋 Members 🦋

get ready, we're doing a member-by-member vibe check 🌈

• data_addr — the VPU address of the payload (the JSM message, iykyk). it's a u32, it's where the goods live ✨
• data_size — the size of the payload. u32. how much of the goods there actually is 📏
• channel — the channel used. u16. which lane the message is travelling in 🛣️
• src_node — the Node ID of the sender. u8. who sent it, main character energy 💌
• dst_node — the Node ID of the intended receiver. u8. who it's for, the intended recipient bestie 🎯
• status — IPC buffer usage status. u8. the current state of the IPC buffer, no cap 🔥

ngl, keep the types exactly as written — u32 for data_addr and data_size, u16 for channel, and u8 for src_node, dst_node and status. the struct is not asking for your creative input 🙈

---

👑 SEE ALSO 👑

• Kernel file ./drivers/accel/ivpu/ivpu_ipc.h — go read the actual header, bestie, she's right there 📂

---

and that's the whole page, fr fr 🍓 this one came from ./drivers/accel/ivpu, dated October 2026, and she's filed under struct ivpu_ipc_hdr(9) forever and ever 💜🧚