drivers/gpu/drm/amd/include/asic_reg/umc/umc_8_10_0_offset.h

Source file repositories/reference/linux-study-clean/drivers/gpu/drm/amd/include/asic_reg/umc/umc_8_10_0_offset.h

File Facts

System: Linux kernel
Corpus path: drivers/gpu/drm/amd/include/asic_reg/umc/umc_8_10_0_offset.h
Extension: .h
Size: 1735 bytes
Lines: 36
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.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef _umc_8_10_0_OFFSET_HEADER
#define _umc_8_10_0_OFFSET_HEADER

#define regUMCCH0_0_GeccErrCntSel                0x0328
#define regUMCCH0_0_GeccErrCntSel_BASE_IDX       2
#define regUMCCH0_0_GeccErrCnt                   0x0329
#define regUMCCH0_0_GeccErrCnt_BASE_IDX          2
#define regMCA_UMC_UMC0_MCUMC_STATUST0           0x03c2
#define regMCA_UMC_UMC0_MCUMC_STATUST0_BASE_IDX  2
#define regMCA_UMC_UMC0_MCUMC_ADDRT0             0x03c4
#define regMCA_UMC_UMC0_MCUMC_ADDRT0_BASE_IDX    2
#define regUMCCH0_0_GeccCtrl                     0x0053
#define regUMCCH0_0_GeccCtrl_BASE_IDX            2

#endif

Annotation

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.