STRUCT MTK_JPEG_VARIANT(9)

okay so bestie, welcome to the Kernel API Manual section 9, where we're gonna talk about struct mtk_jpeg_variant 💅 this is the page for struct mtk_jpeg_variant(9) and it's literally the blueprint for a specific mtk jpeg driver variant, no cap.

✨ NAME ✨

struct mtk_jpeg_variant — the mtk jpeg driver variant struct. it's giving "driver's little ID card plus toolbox" energy 🎀 like, every variant of the MediaTek JPEG hardware gets one of these to tell the driver what it's working with.

🌈 SYNOPSIS 🌈

       struct mtk_jpeg_variant {
           struct clk_bulk_data *clks;
           int num_clks;
           struct mtk_jpeg_fmt *formats;
           int num_formats;
           const struct vb2_ops *qops;
           irqreturn_t (*irq_handler)(int irq, void *priv);
           void (*hw_reset)(void __iomem *base);
           const struct v4l2_m2m_ops *m2m_ops;
           const char *dev_name;
           const struct v4l2_ioctl_ops *ioctl_ops;
           u32 out_q_default_fourcc;
           u32 cap_q_default_fourcc;
           bool multi_core;
           void (*jpeg_worker)(struct work_struct *work);
           bool support_34bit;
        };

💖 Members 💖

• clks — the clock names — like, which clocks this variant needs to function, bestie 💅
• num_clks — the number of clocks — how many clocks there are, fr fr 🔢
• formats — the jpeg driver's internal color format — the secret sauce of how it sees colors 🌈
• num_formats — the number of formats — how many formats are in that list, periodt ✨
• qops — the callback for jpeg vb2_ops — the videobuf2 ops, iykyk 🎀
• irq_handler — the jpeg IRQ handler callback — what runs when the hardware interrupts, like "hey bestie, I'm done" 😭
• hw_reset — the jpeg hardware reset callback — the "turn it off and on again" function 💀
• m2m_ops — the callback for jpeg v4l2_m2m_ops — memory-to-memory ops, the whole pipeline vibe 🦋
• dev_name — the jpeg device name — literally the name of the device, its government name 👑
• ioctl_ops — the callback for jpeg v4l2_ioctl_ops — all the ioctl handlers, the control freak energy 💅
• out_q_default_fourcc — the output queue default fourcc — the pixel format the output queue starts with, no cap 🧢
• cap_q_default_fourcc — the capture queue default fourcc — same vibe but for the capture side, periodt 🍓
• multi_core — a flag marking whether the jpeg hardware is multi-core or not — like, does it have main character energy with multiple cores? 🔥
• jpeg_worker — the jpeg decode or encode worker — the function that gets the work done, the backbone of the operation 😤
• support_34bit — a flag to check support for 34-bit DMA addresses — 34, not 32, not 64, exactly 34, iconic 💜

🦋 SEE ALSO 🦋

go check out these other icons in ./drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.h:

• enum mtk_jpeg_ctx_state(9)
• struct mtk_jpegenc_clk(9)
• struct mtk_jpegdec_clk(9)
• struct mtk_jpegenc_comp_dev(9)
• struct mtk_jpegdec_comp_dev(9)
• struct mtk_jpeg_dev(9)
• struct mtk_jpeg_fmt(9)
• struct mtk_jpeg_q_data(9)
• struct mtk_jpeg_ctx(9)

and that's the whole vibe! this page is from ./drivers/media/platform/media... — October 2026, and it's literally called struct mtk_jpeg_variant(9) if you need to find it again. slay 💅✨