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

File Facts

System

Linux kernel

Corpus path

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

Extension

.c

Size

1845 bytes

Lines

58

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

• priv.h
• rm/gpu.h

Detected Declarations

• function files
• function r535_vfn_new

Annotated Snippet

#include "priv.h"

#include <rm/gpu.h>

static void
r535_vfn_dtor(struct nvkm_vfn *vfn)
{
	kfree(vfn->func);
}

int
r535_vfn_new(const struct nvkm_vfn_func *hw,
	     struct nvkm_device *device, enum nvkm_subdev_type type, int inst, u32 addr,
	     struct nvkm_vfn **pvfn)
{
	const struct nvkm_rm_gpu *gpu = device->gsp->rm->gpu;
	struct nvkm_vfn_func *rm;
	int ret;

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

	rm->dtor = r535_vfn_dtor;
	rm->intr = &tu102_vfn_intr;
	rm->user.addr = 0x030000;
	rm->user.size = 0x010000;
	rm->user.base.minver = -1;
	rm->user.base.maxver = -1;
	rm->user.base.oclass = gpu->usermode.class;

	ret = nvkm_vfn_new_(rm, device, type, inst, addr, pvfn);
	if (ret)
		kfree(rm);

	return ret;
}

Annotation

• Immediate include surface: `priv.h`, `rm/gpu.h`.
• Detected declarations: `function files`, `function r535_vfn_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.