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

File Facts

System

Linux kernel

Corpus path

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

Extension

.c

Size

1758 bytes

Lines

57

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/timer.h
• nvif/device.h

Detected Declarations

• function files
• function nvif_timer_wait_init

Annotated Snippet

#include <nvif/timer.h>
#include <nvif/device.h>

s64
nvif_timer_wait_test(struct nvif_timer_wait *wait)
{
	u64 time = nvif_device_time(wait->device);

	if (wait->reads == 0) {
		wait->time0 = time;
		wait->time1 = time;
	}

	if (wait->time1 == time) {
		if (WARN_ON(wait->reads++ == 16))
			return -ETIMEDOUT;
	} else {
		wait->time1 = time;
		wait->reads = 1;
	}

	if (wait->time1 - wait->time0 > wait->limit)
		return -ETIMEDOUT;

	return wait->time1 - wait->time0;
}

void
nvif_timer_wait_init(struct nvif_device *device, u64 nsec,
		     struct nvif_timer_wait *wait)
{
	wait->device = device;
	wait->limit = nsec;
	wait->reads = 0;
}

Annotation

• Immediate include surface: `nvif/timer.h`, `nvif/device.h`.
• Detected declarations: `function files`, `function nvif_timer_wait_init`.
• 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.