STRUCT GSC_DEV(9)

💅 struct gsc_dev(9) — like, the whole G-Scaler entity, bestie

okay so real talk: this is a page from the Kernel API Manual, and it's all about struct gsc_dev — the abstraction for a G-Scaler entity. no cap, it's the main-character struct of the whole G-Scaler situation, and once you see the members you're gonna get it. 🎀

✨ NAME ✨

struct gsc_dev — the abstraction for a G-Scaler entity. that's it, that's the vibe. 🦋

🌸 SYNOPSIS 🌸

struct gsc_dev {
    spinlock_t slock;
    struct mutex                    lock;
    struct platform_device          *pdev;
    struct gsc_variant              *variant;
    u16 id;
    int num_clocks;
    struct clk                      *clock[GSC_MAX_CLOCKS];
    void __iomem                    *regs;
    wait_queue_head_t irq_queue;
    struct gsc_m2m_device           m2m;
    unsigned long                   state;
    struct video_device             vdev;
    struct v4l2_device              v4l2_dev;
 };

like, look at her. she's got locks, she's got clocks, she's got a whole register map. iconic behavior tbh. 👑

🫶 Members 🫶

• slock — the spinlock that protects this data structure. short, fast, absolutely not here to wait around for you. ⚡
• lock — the mutex protecting this data structure. the patient one. she'll wait her turn, respectfully. 💅
• pdev — pointer to the G-Scaler platform device. it's giving "where you actually came from." 🐣
• variant — the IP variant information. iykyk — every chip's a little different, bestie. 🧚
• id — the G-Scaler device index, and it lives in the range 0..GSC_MAX_DEVS. know your number. 🔢
• num_clocks — how many clocks are required for G-Scaler operation. not optional, fr fr. ⏰
• clock — the clocks required for G-Scaler operation. yes, it's the array, and yes, it's literally called clock. 🌈
• regs — the mapped hardware registers. this is where the actual hardware gossip lives. 🔥
• irq_queue — the interrupt handler waitqueue. somebody's waiting on an interrupt and it's her. 😭
• m2m — memory-to-memory V4L2 device information. the m2m of it all. 🦋
• state — flags used to synchronize m2m and capture mode operation. keeping the two modes from fighting in the group chat. 🫶
• vdev — the video device for this G-Scaler instance. main character energy, obviously. 📹
• v4l2_dev — the v4l2_device for this G-Scaler instance. the V4L2 side of the story. 💜

👀 SEE ALSO 👀

kernel file ./drivers/media/platform/samsung/exynos-gsc/gsc-core.h — that's the source of truth, go read her. and then the whole friend group: enum gsc_datapath(9), struct gsc_fmt(9), struct gsc_input_buf(9), struct gsc_addr(9), struct gsc_scaler(9), struct gsc_frame(9), struct gsc_m2m_device(9), struct gsc_pix_max(9), struct gsc_pix_min(9), struct gsc_driverdata(9), struct gsc_ctx(9).

lowkey a whole ensemble cast. click through them, bestie, they're all connected. 🎀

and that's the page!! mwah 💋 — this one came from ./drivers/media/platform/samsu..., dated October 2026, and the header said struct gsc_dev(9) on both sides like bookends. slay. ✨🌸💖