drivers/gpu/drm/nouveau/dispnv50/oimm.c

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/nouveau/dispnv50/oimm.c

Extension

.c

Size

1846 bytes

Lines

52

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

• oimm.h
• nvif/class.h

Detected Declarations

• function files

Annotated Snippet

#include "oimm.h"

#include <nvif/class.h>

int
nv50_oimm_init(struct nouveau_drm *drm, struct nv50_wndw *wndw)
{
	static const struct {
		s32 oclass;
		int version;
		int (*init)(struct nouveau_drm *, s32, struct nv50_wndw *);
	} oimms[] = {
		{ GK104_DISP_OVERLAY, 0, oimm507b_init },
		{ GF110_DISP_OVERLAY, 0, oimm507b_init },
		{ GT214_DISP_OVERLAY, 0, oimm507b_init },
		{   G82_DISP_OVERLAY, 0, oimm507b_init },
		{  NV50_DISP_OVERLAY, 0, oimm507b_init },
		{}
	};
	struct nv50_disp *disp = nv50_disp(drm->dev);
	int cid;

	cid = nvif_mclass(&disp->disp->object, oimms);
	if (cid < 0) {
		NV_ERROR(drm, "No supported overlay immediate class\n");
		return cid;
	}

	return oimms[cid].init(drm, oimms[cid].oclass, wndw);
}

Annotation

• Immediate include surface: `oimm.h`, `nvif/class.h`.
• Detected declarations: `function files`.
• 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.