drivers/gpu/drm/etnaviv/etnaviv_dump.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/etnaviv/etnaviv_dump.h

Extension

.h

Size

687 bytes

Lines

43

Domain

Driver Families

Bucket

drivers/gpu

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

Detected Declarations

• struct etnaviv_dump_object_header
• struct etnaviv_dump_registers
• struct etnaviv_gem_submit

Annotated Snippet

struct etnaviv_dump_object_header {
	__le32 magic;
	__le32 type;
	__le32 file_offset;
	__le32 file_size;
	__le64 iova;
	__le32 data[2];
};

/* Registers object, an array of these */
struct etnaviv_dump_registers {
	__le32 reg;
	__le32 value;
};

#ifdef __KERNEL__
struct etnaviv_gem_submit;
void etnaviv_core_dump(struct etnaviv_gem_submit *submit);
#endif

#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct etnaviv_dump_object_header`, `struct etnaviv_dump_registers`, `struct etnaviv_gem_submit`.
• Atlas domain: Driver Families / drivers/gpu.
• 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.