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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

798 bytes

Lines

34

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_conn_v0
• struct nvif_conn_event_v0

Annotated Snippet

struct nvif_conn_v0 {
		__u8 version;
		__u8 id;	/* DCB connector table index. */
		__u8 pad02[6];
#define NVIF_CONN_V0_VGA       0x00
#define NVIF_CONN_V0_TV        0x01
#define NVIF_CONN_V0_DVI_I     0x02
#define NVIF_CONN_V0_DVI_D     0x03
#define NVIF_CONN_V0_LVDS      0x04
#define NVIF_CONN_V0_LVDS_SPWG 0x05
#define NVIF_CONN_V0_HDMI      0x06
#define NVIF_CONN_V0_DP        0x07
#define NVIF_CONN_V0_EDP       0x08
		__u8 type;
	} v0;
};

union nvif_conn_event_args {
	struct nvif_conn_event_v0 {
		__u8 version;
#define NVIF_CONN_EVENT_V0_PLUG   0x01
#define NVIF_CONN_EVENT_V0_UNPLUG 0x02
#define NVIF_CONN_EVENT_V0_IRQ    0x04
		__u8 types;
		__u8 pad02[6];
	} v0;
};
#endif

Annotation

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