drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/r535/client.c

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/r535/client.c

Extension

.c

Size

1629 bytes

Lines

46

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

• rm/rm.h
• nvrm/client.h

Detected Declarations

• function files

Annotated Snippet

#include <rm/rm.h>

#include "nvrm/client.h"

static int
r535_gsp_client_ctor(struct nvkm_gsp_client *client, u32 handle)
{
	NV0000_ALLOC_PARAMETERS *args;

	args = nvkm_gsp_rm_alloc_get(&client->object, handle, NV01_ROOT, sizeof(*args),
				     &client->object);
	if (IS_ERR(args))
		return PTR_ERR(args);

	args->hClient = client->object.handle;
	args->processID = ~0;

	return nvkm_gsp_rm_alloc_wr(&client->object, args);
}

const struct nvkm_rm_api_client
r535_client = {
	.ctor = r535_gsp_client_ctor,
};

Annotation

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