drivers/gpu/drm/nouveau/nvkm/subdev/devinit/r535.c

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/nouveau/nvkm/subdev/devinit/r535.c

Extension

.c

Size

1680 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.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• nv50.h

Detected Declarations

• function files
• function r535_devinit_new

Annotated Snippet

#include "nv50.h"

static void *
r535_devinit_dtor(struct nvkm_devinit *devinit)
{
	kfree(devinit->func);
	return devinit;
}

int
r535_devinit_new(const struct nvkm_devinit_func *hw,
		 struct nvkm_device *device, enum nvkm_subdev_type type, int inst,
		 struct nvkm_devinit **pdevinit)
{
	struct nvkm_devinit_func *rm;
	int ret;

	if (!(rm = kzalloc_obj(*rm)))
		return -ENOMEM;

	rm->dtor = r535_devinit_dtor;
	rm->post = hw->post;
	rm->disable = hw->disable;

	ret = nv50_devinit_new_(rm, device, type, inst, pdevinit);
	if (ret)
		kfree(rm);

	return ret;
}

Annotation

• Immediate include surface: `nv50.h`.
• Detected declarations: `function files`, `function r535_devinit_new`.
• 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.