drivers/media/test-drivers/visl/visl-video.h

File Facts

System

Linux kernel

Corpus path

drivers/media/test-drivers/visl/visl-video.h

Extension

.h

Size

830 bytes

Lines

29

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

• media/v4l2-mem2mem.h
• visl.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef _VISL_VIDEO_H_
#define _VISL_VIDEO_H_
#include <media/v4l2-mem2mem.h>

#include "visl.h"

extern const struct v4l2_ioctl_ops visl_ioctl_ops;

extern const struct visl_ctrls visl_fwht_ctrls;
extern const struct visl_ctrls visl_mpeg2_ctrls;
extern const struct visl_ctrls visl_vp8_ctrls;
extern const struct visl_ctrls visl_vp9_ctrls;
extern const struct visl_ctrls visl_h264_ctrls;
extern const struct visl_ctrls visl_hevc_ctrls;
extern const struct visl_ctrls visl_av1_ctrls;

int visl_queue_init(void *priv, struct vb2_queue *src_vq,
		    struct vb2_queue *dst_vq);

int visl_set_default_format(struct visl_ctx *ctx);
int visl_request_validate(struct media_request *req);

#endif /* _VISL_VIDEO_H_ */

Annotation

• Immediate include surface: `media/v4l2-mem2mem.h`, `visl.h`.
• 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.