drivers/gpu/drm/amd/include/asic_reg/smuio/smuio_11_0_6_offset.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/include/asic_reg/smuio/smuio_11_0_6_offset.h

Extension

.h

Size

1917 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 _smuio_11_0_6_OFFSET_HEADER
#define _smuio_11_0_6_OFFSET_HEADER



// addressBlock: smuio_smuio_SmuSmuioDec
// base address: 0x5a000
#define mmCGTT_ROM_CLK_CTRL0                                                                           0x00e4
#define mmCGTT_ROM_CLK_CTRL0_BASE_IDX                                                                  0
#define mmROM_INDEX                                                                                    0x00e5
#define mmROM_INDEX_BASE_IDX                                                                           0
#define mmROM_DATA                                                                                     0x00e6
#define mmROM_DATA_BASE_IDX                                                                            0

#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.