drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/gpu.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/gpu.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/gpu.h- Extension
.h- Size
- 1066 bytes
- Lines
- 71
- 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
rm.h
Detected Declarations
struct nvkm_rm_gpu
Annotated Snippet
struct nvkm_rm_gpu {
struct {
struct {
u32 root;
u32 caps;
u32 core;
u32 wndw;
u32 wimm;
u32 curs;
} class;
} disp;
struct {
u32 class;
} usermode;
struct {
struct {
u32 class;
u32 (*doorbell_handle)(struct nvkm_chan *);
} chan;
} fifo;
struct {
u32 class;
u32 (*grce_mask)(struct nvkm_device *);
} ce;
struct {
struct {
u32 i2m;
u32 twod;
u32 threed;
u32 compute;
} class;
} gr;
struct {
u32 class;
} nvdec;
struct {
u32 class;
} nvenc;
struct {
u32 class;
} nvjpg;
struct {
u32 class;
} ofa;
};
extern const struct nvkm_rm_gpu tu1xx_gpu;
extern const struct nvkm_rm_gpu ga100_gpu;
extern const struct nvkm_rm_gpu ga1xx_gpu;
extern const struct nvkm_rm_gpu ad10x_gpu;
extern const struct nvkm_rm_gpu gh100_gpu;
extern const struct nvkm_rm_gpu gb10x_gpu;
extern const struct nvkm_rm_gpu gb20x_gpu;
#endif
Annotation
- Immediate include surface: `rm.h`.
- Detected declarations: `struct nvkm_rm_gpu`.
- 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.