drivers/gpu/drm/nouveau/include/nvif/if0020.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/nouveau/include/nvif/if0020.h

Extension

.h

Size

791 bytes

Lines

46

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct nvif_chan_v0
• struct nvif_chan_event_v0

Annotated Snippet

struct nvif_chan_v0 {
		__u8  version;
		__u8  namelen;
		__u8  runlist;
		__u8  runq;
		__u8  priv;
		__u8  pad05;
		__u16 devm;
		__u64 vmm;

		__u64 ctxdma;
		__u64 offset;
		__u64 length;

		__u64 huserd;
		__u64 ouserd;

		__u32 token;
		__u16 chid;
		__u8  pad3e;
#define NVIF_CHAN_V0_INST_APER_VRAM 0
#define NVIF_CHAN_V0_INST_APER_HOST 1
#define NVIF_CHAN_V0_INST_APER_NCOH 2
#define NVIF_CHAN_V0_INST_APER_INST 0xff
		__u8  aper;
		__u64 inst;

		__u8  name[];
	} v0;
};

union nvif_chan_event_args {
	struct nvif_chan_event_v0 {
		__u8 version;
#define NVIF_CHAN_EVENT_V0_NON_STALL_INTR 0x00
#define NVIF_CHAN_EVENT_V0_KILLED         0x01
		__u8 type;
	} v0;
};
#endif

Annotation

• Detected declarations: `struct nvif_chan_v0`, `struct nvif_chan_event_v0`.
• 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.