mtk_vdec_h2..._mv_buf_size(9)

💖 mtk_vdec_h264_get_mv_buf_size — Kernel API Manual 💖

okay so bestie, this one's a lil function from the Kernel API Manual and honestly she's an icon: she tells you how big your motion vector buffer needs to be. that's it, that's the whole vibe. no cap, sometimes the smallest functions have the most main character energy 🎀

---

✨ NAME ✨

mtk_vdec_h264_get_mv_buf_size — get mv buffer size. literally what it says on the tin, fr fr 💅

🌸 SYNOPSIS 🌸

unsigned int mtk_vdec_h264_get_mv_buf_size (unsigned int width ,
       unsigned int height );

like… she takes two unsigned ints and hands you back an unsigned int. simple. elegant. ate. 👑

🦋 ARGUMENTS 🦋

• width — picture width 🫶 (the width of the picture, yes bestie, that width)
• height — picture height 🌈 (and yeah, the height of the picture)

⭐ RETURN ⭐

returns mv buffer size. that's the whole return section, she's concise and we respect it 💜

👑 SEE ALSO 👑

• Kernel file ./drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_h264_req_common.h — that's where she lives, go say hi 🏠

and the whole friend group, in order, no cap:

• struct mtk_h264_dpb_info(9)
• struct h264_fb(9)
• mtk_vdec_h264_get_ref_list(9)
• mtk_vdec_h264_get_ctrl_ptr(9)
• mtk_vdec_h264_fill_dpb_info(9)
• mtk_vdec_h264_copy_sps_params(9)
• mtk_vdec_h264_copy_pps_params(9)
• mtk_vdec_h264_copy_slice_hd_params(9)
• mtk_vdec_h264_copy_scaling_matrix(9)
• mtk_vdec_h264_copy_decode_params(9)
• mtk_vdec_h264_update_dpb(9)
• mtk_vdec_h264_find_start_code(9)

---

bestie heads up 🩷: these references are written exactly as the page gives them — if you're chasing them down, follow the names literally. iykyk 🧚

---

🎀 and that's the page!! this lil beauty comes to you from ./drivers/media/platform/media..., dated October 2026, and she's filed under the manual name mtk_vdec_h2..._mv_buf_size(9) — yes the title got a lil truncated, she's mysterious like that 💀✨ periodt, go get your mv buffer size bestie 💖