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

File Facts

System

Linux kernel

Corpus path

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

Extension

.c

Size

1794 bytes

Lines

52

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

• pad.h
• auxch.h
• bus.h

Detected Declarations

• function gf119_i2c_pad_s_new
• function gf119_i2c_pad_x_new

Annotated Snippet

#include "pad.h"
#include "auxch.h"
#include "bus.h"

static const struct nvkm_i2c_pad_func
gf119_i2c_pad_s_func = {
	.bus_new_4 = gf119_i2c_bus_new,
	.aux_new_6 = gf119_i2c_aux_new,
	.mode = g94_i2c_pad_mode,
};

int
gf119_i2c_pad_s_new(struct nvkm_i2c *i2c, int id, struct nvkm_i2c_pad **ppad)
{
	return nvkm_i2c_pad_new_(&gf119_i2c_pad_s_func, i2c, id, ppad);
}

static const struct nvkm_i2c_pad_func
gf119_i2c_pad_x_func = {
	.bus_new_4 = gf119_i2c_bus_new,
	.aux_new_6 = gf119_i2c_aux_new,
};

int
gf119_i2c_pad_x_new(struct nvkm_i2c *i2c, int id, struct nvkm_i2c_pad **ppad)
{
	return nvkm_i2c_pad_new_(&gf119_i2c_pad_x_func, i2c, id, ppad);
}

Annotation

• Immediate include surface: `pad.h`, `auxch.h`, `bus.h`.
• Detected declarations: `function gf119_i2c_pad_s_new`, `function gf119_i2c_pad_x_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.