drivers/gpu/drm/amd/include/ivsrcid/vmc/irqsrcs_vmc_1_0.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/include/ivsrcid/vmc/irqsrcs_vmc_1_0.h

Extension

.h

Size

1756 bytes

Lines

40

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 __IRQSRCS_VMC_1_0_H__
#define __IRQSRCS_VMC_1_0_H__


#define VMC_1_0__SRCID__VM_FAULT                            0
#define VMC_1_0__SRCID__VM_RETRY                            1
#define VMC_1_0__SRCID__VM_CONTEXT0_ALL                     256
#define VMC_1_0__SRCID__VM_CONTEXT1_ALL                     257

#define UTCL2_1_0__SRCID__FAULT                             0       /* UTC L2 has encountered a fault or retry scenario */
#define UTCL2_1_0__SRCID__RETRY                             1       /* UTC L2 has encountered a retry scenario (GFX12.1) */


#endif /* __IRQSRCS_VMC_1_0_H__ */

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.