drivers/gpu/drm/nouveau/nvkm/subdev/i2c/gm200.c

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/nouveau/nvkm/subdev/i2c/gm200.c

Extension

.c

Size

1826 bytes

Lines

54

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

• priv.h
• pad.h
• subdev/gsp.h

Detected Declarations

• function files
• function gm200_i2c_new

Annotated Snippet

#include "priv.h"
#include "pad.h"

#include <subdev/gsp.h>

static void
gm200_aux_autodpcd(struct nvkm_i2c *i2c, int aux, bool enable)
{
	nvkm_mask(i2c->subdev.device, 0x00d968 + (aux * 0x50), 0x00010000, enable << 16);
}

static const struct nvkm_i2c_func
gm200_i2c = {
	.pad_x_new = gf119_i2c_pad_x_new,
	.pad_s_new = gm200_i2c_pad_s_new,
	.aux = 8,
	.aux_stat = gk104_aux_stat,
	.aux_mask = gk104_aux_mask,
	.aux_autodpcd = gm200_aux_autodpcd,
};

int
gm200_i2c_new(struct nvkm_device *device, enum nvkm_subdev_type type, int inst,
	      struct nvkm_i2c **pi2c)
{
	if (nvkm_gsp_rm(device->gsp))
		return -ENODEV;

	return nvkm_i2c_new_(&gm200_i2c, device, type, inst, pi2c);
}

Annotation

• Immediate include surface: `priv.h`, `pad.h`, `subdev/gsp.h`.
• Detected declarations: `function files`, `function gm200_i2c_new`.
• 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.