drivers/gpu/drm/nouveau/nvkm/engine/mpeg/nv31.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/nouveau/nvkm/engine/mpeg/nv31.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/nouveau/nvkm/engine/mpeg/nv31.h- Extension
.h- Size
- 846 bytes
- Lines
- 33
- 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
priv.hengine/mpeg.hcore/object.h
Detected Declarations
struct nv31_mpegstruct nv31_mpeg_funcstruct nv31_mpeg_chan
Annotated Snippet
struct nv31_mpeg {
const struct nv31_mpeg_func *func;
struct nvkm_engine engine;
struct nv31_mpeg_chan *chan;
};
int nv31_mpeg_new_(const struct nv31_mpeg_func *, struct nvkm_device *, enum nvkm_subdev_type, int,
struct nvkm_engine **);
struct nv31_mpeg_func {
bool (*mthd_dma)(struct nvkm_device *, u32 mthd, u32 data);
};
#define nv31_mpeg_chan(p) container_of((p), struct nv31_mpeg_chan, object)
#include <core/object.h>
struct nv31_mpeg_chan {
struct nvkm_object object;
struct nv31_mpeg *mpeg;
struct nvkm_chan *fifo;
};
int nv31_mpeg_chan_new(struct nvkm_chan *, const struct nvkm_oclass *,
struct nvkm_object **);
#endif
Annotation
- Immediate include surface: `priv.h`, `engine/mpeg.h`, `core/object.h`.
- Detected declarations: `struct nv31_mpeg`, `struct nv31_mpeg_func`, `struct nv31_mpeg_chan`.
- 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.