drivers/media/test-drivers/vivid/vivid-meta-out.h
Source file repositories/reference/linux-study-clean/drivers/media/test-drivers/vivid/vivid-meta-out.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/test-drivers/vivid/vivid-meta-out.h- Extension
.h- Size
- 652 bytes
- Lines
- 26
- 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
- No C-style include directives detected by the generator.
Detected Declarations
struct vivid_meta_out_buf
Annotated Snippet
struct vivid_meta_out_buf {
u16 brightness;
u16 contrast;
u16 saturation;
s16 hue;
};
void vivid_meta_out_process(struct vivid_dev *dev, struct vivid_buffer *buf);
int vidioc_enum_fmt_meta_out(struct file *file, void *priv,
struct v4l2_fmtdesc *f);
int vidioc_g_fmt_meta_out(struct file *file, void *priv,
struct v4l2_format *f);
int vidioc_s_fmt_meta_out(struct file *file, void *priv,
struct v4l2_format *f);
extern const struct vb2_ops vivid_meta_out_qops;
#endif
Annotation
- Detected declarations: `struct vivid_meta_out_buf`.
- 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.