STRUCT FIMC_DEV(9)

💖 struct fimc_dev — abstraction for FIMC entity 💖

okay bestie, gather round, because this is the big one in the FIMC corner of the kernel: struct fimc_dev is literally the whole-vibe abstraction for a FIMC entity ✨ It's the main character struct that everything else in this driver orbits around. This page lives in the Kernel API Manual, section 9 (that's the kernel-symbols girlies), and honestly? Obsessed.

---

🌸 SYNOPSIS 🌸

Here's the whole shape of her, verbatim, no cap — copy it exactly, don't you dare retype it by hand 🙈

struct fimc_dev {
    spinlock_t slock;
    struct mutex                    lock;
    struct platform_device          *pdev;
    struct s5p_platform_fimc        *pdata;
    struct regmap                   *sysreg;
    const struct fimc_variant       *variant;
    const struct fimc_drvdata       *drv_data;
    int id;
    struct clk                      *clock[MAX_FIMC_CLOCKS];
    void __iomem                    *regs;
    wait_queue_head_t irq_queue;
    struct v4l2_device              *v4l2_dev;
    struct fimc_m2m_device          m2m;
    struct fimc_vid_cap             vid_cap;
    unsigned long                   state;
 };

---

🎀 Members 🎀

like, member by member, here's who's who in the group chat 💅

• slock — the spinlock guarding this data structure 🌀 short and spicy, don't sleep in it.
• lock — the mutex guarding this data structure 🔐 the chill, can-take-a-nap version of protection.
• pdev — pointer to the FIMC platform device 🧚
• pdata — pointer to the device platform data 🍓
• sysreg — pointer to the SYSREG regmap 🗺️
• variant — the IP variant information 👑 tells you which flavour of silicon you're dealing with.
• drv_data — driver data 📦
• id — FIMC device index (0..FIMC_MAX_DEVS) 🔢 literally her number in the lineup.
• clock — clocks required for FIMC operation ⏰ yes, plural, it's giving MAX_FIMC_CLOCKS of them.
• regs — the mapped hardware registers 🖥️ (void __iomem *, so you know it's the real hardware door.)
• irq_queue — interrupt handler waitqueue 🌙 where everyone waits for the interrupt to show up.
• v4l2_dev — root v4l2_device 📺
• m2m — memory-to-memory V4L2 device information 🔁
• vid_cap — camera capture device information 📷
• state — flags used to synchronize m2m and capture mode operation 🚦 the referee between the two modes, lowkey the most important job here.

---

🦋 SEE ALSO 🦋

go read the source, bestie, it's right here in the kernel tree:

Kernel file ./drivers/media/platform/samsung/exynos4-is/fimc-core.h

and the whole friend group, fr fr:

• struct fimc_dma_offset(9)
• struct fimc_effect(9)
• struct fimc_scaler(9)
• struct fimc_addr(9)
• struct fimc_vid_buffer(9)
• struct fimc_frame(9)
• struct fimc_m2m_device(9)
• struct fimc_vid_cap(9)
• struct fimc_pix_limit(9)
• struct fimc_variant(9)
• struct fimc_drvdata(9)
• struct fimc_ctrls(9)
• struct fimc_ctx(9)
• fimc_active_queue_add(9)
• fimc_active_queue_pop(9)
• fimc_pending_queue_add(9)
• fimc_pending_queue_pop(9)

---

💀 tiny heads-up: slock and lock are both here protecting this same struct — two different lock types, two different rules, so know which one you're holding before you touch anything. no cap, that's the classic oopsie.

---

okay that's the whole page, you ate that 🫶 this gem comes from ./drivers/media/platform/samsu... and it's dated October 2026 — so go forth, read the header file, and slay your FIMC bring-up, bestie 💜🌈⭐