drivers/gpu/drm/amd/amdgpu/amdgpu_ras_eeprom.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/amdgpu/amdgpu_ras_eeprom.h

Extension

.h

Size

5728 bytes

Lines

202

Domain

Driver Families

Bucket

drivers/gpu

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/i2c.h

Detected Declarations

• struct amdgpu_device
• struct amdgpu_ras_eeprom_table_header
• struct amdgpu_ras_eeprom_table_ras_info
• struct amdgpu_ras_eeprom_control
• struct eeprom_table_record
• enum amdgpu_ras_gpu_health_status
• enum amdgpu_ras_eeprom_err_type

Annotated Snippet

extern const struct file_operations amdgpu_ras_debugfs_eeprom_size_ops;
extern const struct file_operations amdgpu_ras_debugfs_eeprom_table_ops;

#endif // _AMDGPU_RAS_EEPROM_H

Annotation

• Immediate include surface: `linux/i2c.h`.
• Detected declarations: `struct amdgpu_device`, `struct amdgpu_ras_eeprom_table_header`, `struct amdgpu_ras_eeprom_table_ras_info`, `struct amdgpu_ras_eeprom_control`, `struct eeprom_table_record`, `enum amdgpu_ras_gpu_health_status`, `enum amdgpu_ras_eeprom_err_type`.
• Atlas domain: Driver Families / drivers/gpu.
• Implementation status: pattern 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.