drivers/gpu/drm/amd/include/asic_reg/umc/umc_8_14_0_sh_mask.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/amd/include/asic_reg/umc/umc_8_14_0_sh_mask.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/amd/include/asic_reg/umc/umc_8_14_0_sh_mask.h- Extension
.h- Size
- 1937 bytes
- Lines
- 38
- 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_14_0_SH_MASK_HEADER
#define _umc_8_14_0_SH_MASK_HEADER
//UMCCH0_GeccErrCntSel
#define UMCCH0_GeccErrCntSel__GeccErrInt__SHIFT 0xc
#define UMCCH0_GeccErrCntSel__GeccErrCntEn__SHIFT 0xf
#define UMCCH0_GeccErrCntSel__PoisonCntEn__SHIFT 0x10
#define UMCCH0_GeccErrCntSel__GeccErrInt_MASK 0x00003000L
#define UMCCH0_GeccErrCntSel__GeccErrCntEn_MASK 0x00008000L
#define UMCCH0_GeccErrCntSel__PoisonCntEn_MASK 0x00030000L
//UMCCH0_GeccErrCnt
#define UMCCH0_GeccErrCnt__GeccErrCnt__SHIFT 0x0
#define UMCCH0_GeccErrCnt__GeccUnCorrErrCnt__SHIFT 0x10
#define UMCCH0_GeccErrCnt__GeccErrCnt_MASK 0x0000FFFFL
#define UMCCH0_GeccErrCnt__GeccUnCorrErrCnt_MASK 0xFFFF0000L
#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.