drivers/gpu/drm/nouveau/nvkm/subdev/therm/fannil.c

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/nouveau/nvkm/subdev/therm/fannil.c

Extension

.c

Size

1587 bytes

Lines

53

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 nvkm_fannil_set
• function nvkm_fannil_create

Annotated Snippet

#include "priv.h"

static int
nvkm_fannil_get(struct nvkm_therm *therm)
{
	return -ENODEV;
}

static int
nvkm_fannil_set(struct nvkm_therm *therm, int percent)
{
	return -ENODEV;
}

int
nvkm_fannil_create(struct nvkm_therm *therm)
{
	struct nvkm_fan *priv;

	priv = kzalloc_obj(*priv);
	therm->fan = priv;
	if (!priv)
		return -ENOMEM;

	priv->type = "none / external";
	priv->get = nvkm_fannil_get;
	priv->set = nvkm_fannil_set;
	return 0;
}

Annotation

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