drivers/staging/media/meson/vdec/vdec_platform.h

File Facts

System

Linux kernel

Corpus path

drivers/staging/media/meson/vdec/vdec_platform.h

Extension

.h

Size

839 bytes

Lines

37

Domain

Driver Families

Bucket

drivers/staging

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

• vdec.h

Detected Declarations

• struct amvdec_format
• struct vdec_platform
• enum vdec_revision

Annotated Snippet

struct vdec_platform {
	const struct amvdec_format *formats;
	const u32 num_formats;
	enum vdec_revision revision;
};

extern const struct vdec_platform vdec_platform_gxbb;
extern const struct vdec_platform vdec_platform_gxm;
extern const struct vdec_platform vdec_platform_gxl;
extern const struct vdec_platform vdec_platform_gxlx;
extern const struct vdec_platform vdec_platform_g12a;
extern const struct vdec_platform vdec_platform_sm1;

#endif

Annotation

• Immediate include surface: `vdec.h`.
• Detected declarations: `struct amvdec_format`, `struct vdec_platform`, `enum vdec_revision`.
• Atlas domain: Driver Families / drivers/staging.
• 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.