drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/engine.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/engine.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/engine.h- Extension
.h- Size
- 704 bytes
- Lines
- 21
- 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
gpu.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef __NVKM_RM_ENGINE_H__
#define __NVKM_RM_ENGINE_H__
#include "gpu.h"
int nvkm_rm_engine_ctor(void *(*dtor)(struct nvkm_engine *), struct nvkm_rm *,
enum nvkm_subdev_type type, int inst,
const u32 *class, int nclass, struct nvkm_engine *);
int nvkm_rm_engine_new(struct nvkm_rm *, enum nvkm_subdev_type, int inst);
int nvkm_rm_engine_obj_new(struct nvkm_gsp_object *chan, int chid, const struct nvkm_oclass *,
struct nvkm_object **);
int nvkm_rm_gr_new(struct nvkm_rm *);
int nvkm_rm_nvdec_new(struct nvkm_rm *, int inst);
int nvkm_rm_nvenc_new(struct nvkm_rm *, int inst);
#endif
Annotation
- Immediate include surface: `gpu.h`.
- 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.