drivers/gpu/drm/nouveau/nvif/driver.c

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/nouveau/nvif/driver.c

Extension

.c

Size

1529 bytes

Lines

41

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/driver.h
• nvif/client.h

Detected Declarations

• function files

Annotated Snippet

#include <nvif/driver.h>
#include <nvif/client.h>

int
nvif_driver_init(const char *drv, const char *cfg, const char *dbg,
		 const char *name, u64 device, struct nvif_client *client)
{
	int ret;

	client->driver = &nvif_driver_nvkm;

	ret = client->driver->init(name, device, cfg, dbg, &client->object.priv);
	if (ret)
		return ret;

	return nvif_client_ctor(client, name, client);
}

Annotation

• Immediate include surface: `nvif/driver.h`, `nvif/client.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.