STRUCT XVIP_COMPOSITE_DEVICE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME

struct xvip_composite_device β€” the Xilinx Video IP device structure, bestie. That's the whole vibe: it's the big container thing for a Xilinx Video IP setup ✨

(this page lives in the Kernel API Manual, section 9, just so u know where u are 🫢)


✨ SYNOPSIS

struct xvip_composite_device {
    struct v4l2_device v4l2_dev;
    struct media_device media_dev;
    struct device *dev;
    struct v4l2_async_notifier notifier;
    struct list_head dmas;
    u32 v4l2_caps;
};

Like, that's the whole struct, no cap. Every field copy-pasted exactly, character for character, because we do not mess with code πŸ’…


πŸŽ€ Members

okay so let's go field by field, bestie, one at a time, no skipping πŸ¦‹

  • v4l2_dev β€” the V4L2 device, literally. That's its whole job 🌸
  • media_dev β€” the media device πŸŽ€
  • dev β€” the (OF) device πŸ‘‘
  • notifier β€” the V4L2 asynchronous subdevs notifier. it notifies. asynchronously. about subdevs. iykyk ✨
  • dmas β€” a list of DMA channels at the pipeline output and input πŸ”₯ both ends of the pipeline, slay
  • v4l2_caps β€” V4L2 capabilities of the whole device (see VIDIOC_QUERYCAP). the whole device, not just a corner of it πŸ’œ
ngl this struct is giving "main character energy" β€” it's holding the v4l2 device, the media device, the device pointer, the notifier, the dma list AND the caps all at once. icon behaviour fr fr 😭

πŸ¦‹ SEE ALSO

  • Kernel file ./drivers/media/platform/xilinx/xilinx-vipp.h β€” go read it, it's right there, it's giving source of truth ⭐

and that's the page, bestie!! πŸ“πŸ’– go forth and composite ur devices, u absolute legend 🧚

shoutout to ./drivers/media/platform/xilinx, dated October 2026, for hosting this whole situation β€” mwah πŸ’‹

πŸ“¦ where this page comes from