drivers/media/platform/chips-media/coda/imx-vdoa.h

File Facts

System

Linux kernel

Corpus path

drivers/media/platform/chips-media/coda/imx-vdoa.h

Extension

.h

Size

1143 bytes

Lines

51

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 vdoa_data
• struct vdoa_ctx
• function vdoa_context_configure
• function vdoa_context_destroy
• function vdoa_device_run
• function vdoa_wait_for_completion

Annotated Snippet

static inline void vdoa_context_destroy(struct vdoa_ctx *ctx) { };

static inline void vdoa_device_run(struct vdoa_ctx *ctx,
				   dma_addr_t dst, dma_addr_t src) { };

static inline int vdoa_wait_for_completion(struct vdoa_ctx *ctx)
{
	return 0;
};

#endif

#endif /* IMX_VDOA_H */

Annotation

• Detected declarations: `struct vdoa_data`, `struct vdoa_ctx`, `function vdoa_context_configure`, `function vdoa_context_destroy`, `function vdoa_device_run`, `function vdoa_wait_for_completion`.
• 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.