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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

576 bytes

Lines

26

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

• nvif/os.h

Detected Declarations

• struct nvif_object
• struct nvif_parent
• function nvif_parent_dtor
• function nvif_parent_ctor

Annotated Snippet

struct nvif_parent {
	const struct nvif_parent_func {
		void (*debugf)(struct nvif_object *, const char *fmt, ...) __printf(2, 3);
		void (*errorf)(struct nvif_object *, const char *fmt, ...) __printf(2, 3);
	} *func;
};

static inline void
nvif_parent_dtor(struct nvif_parent *parent)
{
	parent->func = NULL;
}

static inline void
nvif_parent_ctor(const struct nvif_parent_func *func, struct nvif_parent *parent)
{
	parent->func = func;
}
#endif

Annotation

• Immediate include surface: `nvif/os.h`.
• Detected declarations: `struct nvif_object`, `struct nvif_parent`, `function nvif_parent_dtor`, `function nvif_parent_ctor`.
• 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.