drivers/gpu/drm/amd/amdgpu/smuio_v13_0_6.c
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/amd/amdgpu/smuio_v13_0_6.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/amd/amdgpu/smuio_v13_0_6.c- Extension
.c- Size
- 1699 bytes
- Lines
- 42
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
amdgpu.hsmuio_v13_0_6.hsmuio/smuio_13_0_6_offset.hsmuio/smuio_13_0_6_sh_mask.h
Detected Declarations
function filesfunction smuio_v13_0_6_get_rom_data_offset
Annotated Snippet
#include "amdgpu.h"
#include "smuio_v13_0_6.h"
#include "smuio/smuio_13_0_6_offset.h"
#include "smuio/smuio_13_0_6_sh_mask.h"
static u32 smuio_v13_0_6_get_rom_index_offset(struct amdgpu_device *adev)
{
return SOC15_REG_OFFSET(SMUIO, 0, regROM_INDEX);
}
static u32 smuio_v13_0_6_get_rom_data_offset(struct amdgpu_device *adev)
{
return SOC15_REG_OFFSET(SMUIO, 0, regROM_DATA);
}
const struct amdgpu_smuio_funcs smuio_v13_0_6_funcs = {
.get_rom_index_offset = smuio_v13_0_6_get_rom_index_offset,
.get_rom_data_offset = smuio_v13_0_6_get_rom_data_offset,
};
Annotation
- Immediate include surface: `amdgpu.h`, `smuio_v13_0_6.h`, `smuio/smuio_13_0_6_offset.h`, `smuio/smuio_13_0_6_sh_mask.h`.
- Detected declarations: `function files`, `function smuio_v13_0_6_get_rom_data_offset`.
- 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.