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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

866 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

• linux/platform_device.h
• vdec.h

Detected Declarations

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

Annotated Snippet

#ifndef __MESON_VDEC_ESPARSER_H_
#define __MESON_VDEC_ESPARSER_H_

#include <linux/platform_device.h>

#include "vdec.h"

int esparser_init(struct platform_device *pdev, struct amvdec_core *core);
int esparser_power_up(struct amvdec_session *sess);

/**
 * esparser_queue_eos() - write End Of Stream sequence to the ESPARSER
 *
 * @core: vdec core struct
 * @data: EOS sequence
 * @len: length of EOS sequence
 */
int esparser_queue_eos(struct amvdec_core *core, const u8 *data, u32 len);

/**
 * esparser_queue_all_src() - work handler that writes as many src buffers
 * as possible to the ESPARSER
 *
 * @work: work struct
 */
void esparser_queue_all_src(struct work_struct *work);

#define ESPARSER_MIN_PACKET_SIZE SZ_4K

#endif

Annotation

• Immediate include surface: `linux/platform_device.h`, `vdec.h`.
• 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.