drivers/media/platform/qcom/venus/hfi_plat_bufs.h

File Facts

System

Linux kernel

Corpus path

drivers/media/platform/qcom/venus/hfi_plat_bufs.h

Extension

.h

Size

820 bytes

Lines

42

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

• linux/types.h
• hfi_helper.h

Detected Declarations

• struct hfi_plat_buffers_params

Annotated Snippet

struct hfi_plat_buffers_params {
	u32 width;
	u32 height;
	u32 out_width;
	u32 out_height;
	u32 codec;
	u32 hfi_color_fmt;
	u32 hfi_dpb_color_fmt;
	enum hfi_version version;
	u32 num_vpp_pipes;
	union {
		struct {
			u32 max_mbs_per_frame;
			u32 buffer_size_limit;
			bool is_secondary_output;
			bool is_interlaced;
		} dec;
		struct {
			u32 work_mode;
			u32 rc_type;
			u32 num_b_frames;
			bool is_tenbit;
		} enc;
	};
};

int hfi_plat_bufreq_v6(struct hfi_plat_buffers_params *params, u32 session_type,
		       u32 buftype, struct hfi_buffer_requirements *bufreq);

#endif

Annotation

• Immediate include surface: `linux/types.h`, `hfi_helper.h`.
• Detected declarations: `struct hfi_plat_buffers_params`.
• 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.