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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

1231 bytes

Lines

41

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

• visl.h
• visl-dec.h

Detected Declarations

• function visl_debugfs_init
• function visl_debugfs_bitstream_init
• function visl_trace_bitstream

Annotated Snippet

static inline void visl_trace_bitstream(struct visl_ctx *ctx, struct visl_run *run) {}
static inline void visl_debugfs_clear_bitstream(struct visl_dev *dev) {}
static inline void visl_debugfs_bitstream_deinit(struct visl_dev *dev) {}
static inline void visl_debugfs_deinit(struct visl_dev *dev) {}

#endif

Annotation

• Immediate include surface: `visl.h`, `visl-dec.h`.
• Detected declarations: `function visl_debugfs_init`, `function visl_debugfs_bitstream_init`, `function visl_trace_bitstream`.
• 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.