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

File Facts

System

Linux kernel

Corpus path

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

Extension

.c

Size

1612 bytes

Lines

48

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/user.h

Detected Declarations

• function files
• function nvif_userc361_doorbell

Annotated Snippet

#include <nvif/user.h>

static u64
nvif_userc361_time(struct nvif_user *user)
{
	u32 hi, lo;

	do {
		hi = nvif_rd32(&user->object, 0x084);
		lo = nvif_rd32(&user->object, 0x080);
	} while (hi != nvif_rd32(&user->object, 0x084));

	return ((u64)hi << 32 | lo);
}

static void
nvif_userc361_doorbell(struct nvif_user *user, u32 token)
{
	nvif_wr32(&user->object, 0x90, token);
}

const struct nvif_user_func
nvif_userc361 = {
	.doorbell = nvif_userc361_doorbell,
	.time = nvif_userc361_time,
};

Annotation

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