STRUCT XCSI2RXSS_STATE(9)

💖 struct xcsi2rxss_state(9) — CSI-2 Rx Subsystem device structure 💖

okay bestie, welcome to the Kernel API Manual entry for struct xcsi2rxss_state(9) — the actual main-character struct of the CSI-2 Rx Subsystem. this is the whole vibe-coded dossier of everything the driver needs to keep track of, and we're gonna go through every single field together. no skipping. periodt. ✨

---

🌸 SYNOPSIS 🌸

here's the full struct, exactly as it lives, bestie — do not touch, do not "clean up", just vibe check it:

struct xcsi2rxss_state {
    struct v4l2_subdev subdev;
    struct v4l2_mbus_framefmt format;
    struct v4l2_mbus_framefmt default_format;
    u32 events[XCSI_NUM_EVENTS];
    u32 vcx_events[XCSI_VCX_NUM_EVENTS];
    struct device *dev;
    struct v4l2_subdev *rsubdev;
    struct gpio_desc *rst_gpio;
    struct clk_bulk_data *clks;
    void __iomem *iomem;
    u32 max_num_lanes;
    u32 datatype;
    struct mutex lock;
    struct media_pad pads[XCSI_MEDIA_PADS];
    bool streaming;
    bool enable_active_lanes;
    bool en_vcx;
};

---

🦋 MEMBERS 🦋

every field, one by one, with the lore attached. slay. 💅

• subdev — The v4l2 subdev structure. literally the subdev's whole identity card. 👑
• format — Active V4L2 formats on each pad. this is the currently happening format energy, per pad. 🔥
• default_format — Default V4L2 format. the fallback fit, iykyk. 🎀
• events — counter for events. keeping tally, fr fr. ⭐
• vcx_events — counter for vcx_events. yeah, the vcx-flavoured tally, separate account. 🍓
• dev — Platform structure. the device's home base. 🏠
• rsubdev — Remote subdev connected to sink pad. the neighbor on the other end of the wire, lowkey iconic. 🌈
• rst_gpio — reset to video_aresetn. that's the reset line, bestie, do not poke it for fun. 🙈
• clks — array of clocks. plural. a whole array. tick tock. ⏰
• iomem — Base address of subsystem. where the registers actually live. 💀
• max_num_lanes — Maximum number of lanes present. how many lanes we got, max. 🛣️
• datatype — Data type filter. it decides what data types pass the vibe check. 🧚
• lock — mutex for accessing this structure. do NOT touch the struct without holding this. seriously. it's the rule. 💜
• pads — media pads. the connection points, plural, obviously. 🔌
• streaming — Flag for storing streaming state. are we streaming or are we not, that is the question. 🎥
• enable_active_lanes — If number of active lanes can be modified. basically: is changing the active lane count even allowed rn. 🚦
• en_vcx — If more than 4 VC are enabled. four-plus virtual channels? this flag knows. ✨

---

💫 DESCRIPTION 💫

This structure contains the device driver related parameters. that's it, that's the whole description — but like, it's the entire driver-state brain trust in one struct, so show some respect. 🫶

---

⭐ SEE ALSO ⭐

go read these next, bestie, they're all in the same kernel file:

• Kernel file ./drivers/media/platform/xilinx/xilinx-csi2rxss.c
• struct xcsi2rxss_event(9)
• xcsi2rxss_soft_reset(9)
• xcsi2rxss_irq_handler(9)

---

and that's the page!! 🎀 this little masterpiece lives at ./drivers/media/platform/xilinx, and it's dated October 2026 — so yeah, it's from the future, we stay ahead. mwah, go read the kernel source, ily, bye 💖