drivers/gpu/drm/amd/ras/rascore/ras_mp1.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/ras/rascore/ras_mp1.h

Extension

.h

Size

1966 bytes

Lines

51

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

• ras.h

Detected Declarations

• struct ras_mp1_ip_func
• struct ras_mp1
• enum ras_err_type

Annotated Snippet

struct ras_mp1_ip_func {
	int (*get_valid_bank_count)(struct ras_core_context *ras_core,
			enum ras_err_type type, u32 *count);
	int (*dump_valid_bank)(struct ras_core_context *ras_core,
		enum ras_err_type type, u32 idx, u32 reg_idx, u64 *val);
};

struct ras_mp1 {
	uint32_t mp1_ip_version;
	const struct ras_mp1_ip_func *ip_func;
	const struct ras_mp1_sys_func *sys_func;
};

int ras_mp1_hw_init(struct ras_core_context *ras_core);
int ras_mp1_hw_fini(struct ras_core_context *ras_core);

int ras_mp1_get_bank_count(struct ras_core_context *ras_core,
			    enum ras_err_type type, u32 *count);

int ras_mp1_dump_bank(struct ras_core_context *ras_core,
		u32 ecc_type, u32 idx, u32 reg_idx, u64 *val);
#endif

Annotation

• Immediate include surface: `ras.h`.
• Detected declarations: `struct ras_mp1_ip_func`, `struct ras_mp1`, `enum ras_err_type`.
• 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.