drivers/media/platform/xilinx/xilinx-vipp.h
Source file repositories/reference/linux-study-clean/drivers/media/platform/xilinx/xilinx-vipp.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/platform/xilinx/xilinx-vipp.h- Extension
.h- Size
- 1076 bytes
- Lines
- 43
- Domain
- Driver Families
- Bucket
- drivers/media
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/list.hlinux/mutex.hmedia/media-device.hmedia/v4l2-async.hmedia/v4l2-ctrls.hmedia/v4l2-device.h
Detected Declarations
struct xvip_composite_device
Annotated Snippet
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;
};
#endif /* __XILINX_VIPP_H__ */
Annotation
- Immediate include surface: `linux/list.h`, `linux/mutex.h`, `media/media-device.h`, `media/v4l2-async.h`, `media/v4l2-ctrls.h`, `media/v4l2-device.h`.
- Detected declarations: `struct xvip_composite_device`.
- Atlas domain: Driver Families / drivers/media.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.