STRUCT VDEC_AV1_SLICE_MFMV(9)

🦋 struct vdec_av1_slice_mfmv(9) — the AV1 mfmv parameters glow-up 🎀

okay so bestie, we're in the Kernel API Manual, section 9, and today's main character is struct vdec_av1_slice_mfmv. It's giving "small struct, big job" energy. Let's get into it 💅

---

✨ NAME ✨

struct vdec_av1_slice_mfmv — literally the AV1 mfmv parameters. That's the whole name, that's the whole vibe. No cap.

---

🌸 SYNOPSIS 🌸

here she is in all her glory, copy-pasted with love and zero typos (do not touch, she's fragile):

struct vdec_av1_slice_mfmv {
    u32 mfmv_valid_ref[3];
    u32 mfmv_dir[3];
    int mfmv_ref_to_cur[3];
    int mfmv_ref_frame_idx[3];
    int mfmv_count;
 };

like. look at her. five fields. three-element arrays. u32 and int living together in harmony. we stan a compact struct 💖

---

🫶 Members 🫶

okay so here's the thing — and I need you to sit down for this — the documentation for every single one of these members is just the member name again. That's it. That's the whole description. The kernel-doc said "mfmv_valid_ref" and then, for the description, said "mfmv_valid_ref". Iconic honestly. Zero elaboration. Gatekeeping at its finest 🙈

So without further ado, the full roster, exactly as the page gives it:

• mfmv_valid_ref — the docs say: mfmv_valid_ref. yes queen, we know ✨
• mfmv_dir — the docs say: mfmv_dir. short. mysterious. slay 💅
• mfmv_ref_to_cur — the docs say: mfmv_ref_to_cur. no notes 🎀
• mfmv_ref_frame_idx — the docs say: mfmv_ref_frame_idx. truly a legend 🌸
• mfmv_count — the docs say: mfmv_count. the finale. the moment. the count 👑

lowkey ngl, I can't tell you more than the manpage does because the manpage doesn't have more. bestie, I am not about to invent kernel behaviour — that's how you get cursed bugs. so we keep it honest: the descriptions are the names, verbatim, and that's canon 🦋

---

🔥 SEE ALSO 🔥

okay this is where it gets good because our girl does not exist in a vacuum — she's part of a whole friend group, a whole squad of vdec_av1_slice_* structs, and the manpage shouts out every single one. no member left behind fr fr 🫶

Kernel file: ./drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_av1_req_lat_if.c

and the whole group chat:

• struct vdec_av1_slice_init_vsi(9)
• struct vdec_av1_slice_mem(9)
• struct vdec_av1_slice_state(9)
• struct vdec_av1_slice_tile_group(9)
• struct vdec_av1_slice_scale_factors(9)
• struct vdec_av1_slice_frame_refs(9)
• struct vdec_av1_slice_gm(9)
• struct vdec_av1_slice_sm(9)
• struct vdec_av1_slice_seg(9)
• struct vdec_av1_slice_delta_q_lf(9)
• struct vdec_av1_slice_quantization(9)
• struct vdec_av1_slice_lr(9)
• struct vdec_av1_slice_loop_filter(9)
• struct vdec_av1_slice_cdef(9)
• struct vdec_av1_slice_tile(9)
• struct vdec_av1_slice_uncompressed_header(9)
• struct vdec_av1_slice_seq_header(9)
• struct vdec_av1_slice_frame(9)
• struct vdec_av1_slice_work_buffer(9)
• struct vdec_av1_slice_frame_info(9)
• struct vdec_av1_slice_slot(9)
• struct vdec_av1_slice_fb(9)
• struct vdec_av1_slice_vsi(9)
• struct vdec_av1_slice_pfc(9)
• struct vdec_av1_slice_instance(9)

like?? that's twenty-five structs?? the AV1 slice code has more structs than I have unread notifications 😭 and every single one of them is cross-referenced right here. iykyk 💜

---

💖 the sign-off 💖

this little legend comes to us from the Kernel API Manual, page struct vdec_av1_slice_mfmv(9), dated October 2026, sourced from ./drivers/media/platform/media... (yes, the footer truncated the path and we are respecting the truncation, don't @ me 🙈).

go read your structs, hydrate, and remember: if the docs just repeat the field name, that's not a you problem, that's main character documentation energy 🧚 💜 ✨