drivers/media/platform/qcom/iris/iris_hfi_gen2.h

File Facts

System

Linux kernel

Corpus path

drivers/media/platform/qcom/iris/iris_hfi_gen2.h

Extension

.h

Size

1200 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

• iris_instance.h

Detected Declarations

• struct iris_core
• struct iris_inst_hfi_gen2

Annotated Snippet

struct iris_inst_hfi_gen2 {
	struct iris_inst		inst;
	struct iris_hfi_header		*packet;
	bool				ipsc_properties_set;
	bool				opsc_properties_set;
	struct iris_hfi_frame_info	hfi_frame_info;
	struct hfi_subscription_params	src_subcr_params;
	struct hfi_subscription_params	dst_subcr_params;
};

void iris_hfi_gen2_sys_ops_init(struct iris_core *core);
void iris_hfi_gen2_response_handler(struct iris_core *core);

#endif

Annotation

• Immediate include surface: `iris_instance.h`.
• Detected declarations: `struct iris_core`, `struct iris_inst_hfi_gen2`.
• 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.