drivers/gpu/drm/imagination/pvr_rogue_fwif_resetframework.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/imagination/pvr_rogue_fwif_resetframework.h

Extension

.h

Size

695 bytes

Lines

29

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/bits.h
• linux/types.h
• pvr_rogue_fwif_shared.h

Detected Declarations

• struct rogue_fwif_rf_registers
• struct rogue_fwif_rf_cmd

Annotated Snippet

struct rogue_fwif_rf_registers {
	union {
		u64 cdmreg_cdm_cb_base;
		u64 cdmreg_cdm_ctrl_stream_base;
	};
	u64 cdmreg_cdm_cb_queue;
	u64 cdmreg_cdm_cb;
};

struct rogue_fwif_rf_cmd {
	/* THIS MUST BE THE LAST MEMBER OF THE CONTAINING STRUCTURE */
	struct rogue_fwif_rf_registers fw_registers __aligned(8);
};

#define ROGUE_FWIF_RF_CMD_SIZE sizeof(struct rogue_fwif_rf_cmd)

#endif /* PVR_ROGUE_FWIF_RESETFRAMEWORK_H */

Annotation

• Immediate include surface: `linux/bits.h`, `linux/types.h`, `pvr_rogue_fwif_shared.h`.
• Detected declarations: `struct rogue_fwif_rf_registers`, `struct rogue_fwif_rf_cmd`.
• 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.