STRUCT VDEC_VPU_INST(9)

💖 struct vdec_vpu_inst(9) — the Kernel API Manual glow-up you didn't know you needed 💖

okay bestie, so this is a page straight out of the Kernel API Manual, and it's about struct vdec_vpu_inst — literally the VPU instance for the video codec. no cap, this is the little data homegirl that holds all the decoder's state. let's get into it 🎀

---

✨ NAME ✨

struct vdec_vpu_inst — VPU instance for video codec 🦋

like, the whole vibe of this struct is "I am one (1) instance of a VPU, and I handle video codec things." iconic behaviour honestly.

---

🌸 SYNOPSIS 🌸

struct vdec_vpu_inst {
    int id;
    int core_id;
    void *vsi;
    int32_t failure;
    uint32_t inst_addr;
    uint32_t fw_abi_version;
    uint32_t inst_id;
    unsigned int signaled;
    struct mtk_vcodec_dec_ctx *ctx;
    wait_queue_head_t wq;
    mtk_vcodec_ipi_handler handler;
    unsigned int codec_type;
    unsigned int capture_type;
    unsigned int fb_sz[2];
 };

look at her. fourteen fields. all of them carrying their little job on their shoulders 😭💅

---

👑 Members 👑

• id — the ipi msg id for each decoder 🆔 — this is how each decoder gets told apart in the message flow.
• core_id — the core id, used to separate different hardware — because not every core is the same core, okay?
• vsi — the driver structure allocated by the VPU side and shared over to the AP side, so the two sides can share control and info 🤝 — a whole little shared hangout spot.
• failure — the VPU execution result status: 0 means success, and anything else means fail 💀 (yes, "others: fail" — that's the actual rule, bestie, don't come for me).
• inst_addr — the VPU decoder instance address 📍 — where the instance lives.
• fw_abi_version — the ABI version of the firmware — important, because the next member literally depends on it 👀.
• inst_id — if fw_abi_version >= 2, this contains the instance ID, and that ID gets given in place of inst_addr in messages. so like... new firmware, new way of pointing at the instance ✨
• signaled — 1 means the host has received the ack message from the VPU; 0 means it has not been received 📬 — the classic "did they text back" flag, fr fr.
• ctx — the context for v4l2 layer integration 🫶 — this is where the v4l2 side plugs in.
• wq — the wait queue used to wait for a VPU message ack ⏳ — the "pls hold, waiting for a reply" line.
• handler — the ipi handler for each decoder 📞 — someone's gotta pick up when the message comes in.
• codec_type — uses codec type to separate different codecs 🎬 — different codec, different bucket.
• capture_type — uses capture type to separate different capture formats 🌈 — same deal, but for capture formats.
• fb_sz — the frame buffer size of each plane 🖼️ — it's an array of two, so one size per plane, mmkay?

side note bestie: fb_sz[2] is literally two entries, one per plane — the doc says "of each plane" and that's the whole tea 🍵

---

🔥 SEE ALSO 🔥

Kernel file:

./drivers/media/platform/mediatek/vcodec/decoder/vdec_vpu_if.h

and the whole friend group 🫶:

• vpu_dec_init(9)
• vpu_dec_start(9)
• vpu_dec_end(9)
• vpu_dec_deinit(9)
• vpu_dec_reset(9)
• vpu_dec_core(9)
• vpu_dec_core_end(9)
• vpu_dec_get_param(9)

---

that's the whole page, bestie — go forth and slay your MediaTek decoder integration 💜✨

🧚 sign-off time: this lil page came from ./drivers/media/platform/media... and it's dated October 2026. mwah 💋 see u in the next manpage 🎀