drivers/gpu/drm/nouveau/nvkm/subdev/acr/ga100.c

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/nouveau/nvkm/subdev/acr/ga100.c

Extension

.c

Size

1904 bytes

Lines

50

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

Detected Declarations

• function files
• function ga100_acr_hsfw_ctor

Annotated Snippet

#include "priv.h"

void
ga100_acr_wpr_check(struct nvkm_acr *acr, u64 *start, u64 *limit)
{
	struct nvkm_device *device = acr->subdev.device;

	*start = (u64)(nvkm_rd32(device, 0x1fa81c) & 0xffffff00) << 8;
	*limit = (u64)(nvkm_rd32(device, 0x1fa820) & 0xffffff00) << 8;
	*limit = *limit + 0x20000;
}

int
ga100_acr_hsfw_ctor(struct nvkm_acr *acr, const char *bl, const char *fw,
		    const char *name, int ver, const struct nvkm_acr_hsf_fwif *fwif)
{
	struct nvkm_acr_hsfw *hsfw;

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

	hsfw->falcon_id = fwif->falcon_id;
	hsfw->boot_mbox0 = fwif->boot_mbox0;
	hsfw->intr_clear = fwif->intr_clear;
	list_add_tail(&hsfw->head, &acr->hsfw);

	return nvkm_falcon_fw_ctor_hs_v2(fwif->func, name, &acr->subdev, fw, ver, NULL, &hsfw->fw);
}

Annotation

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