drivers/gpu/drm/nouveau/nvkm/subdev/bios/ramcfg.c

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/nouveau/nvkm/subdev/bios/ramcfg.c

Extension

.c

Size

2502 bytes

Lines

79

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

• subdev/bios.h
• subdev/bios/bit.h
• subdev/bios/ramcfg.h
• subdev/bios/M0203.h

Detected Declarations

• function files
• function nvbios_ramcfg_count
• function nvbios_ramcfg_index

Annotated Snippet

if (bit_M.version == 2 && bit_M.length >= 3) {
			/*XXX: is M ever shorter than this?
			 *     if not - what is xlat used for now?
			 *     also - sigh..
			 */
			if (bit_M.length >= 7 &&
			    nvbios_M0203Em(bios, strap, &ver, &hdr, &M0203E))
				return M0203E.group;
			xlat = nvbios_rd16(bios, bit_M.offset + 1);
		}
	}

	if (xlat)
		strap = nvbios_rd08(bios, xlat + strap);
	return strap;
}

Annotation

• Immediate include surface: `subdev/bios.h`, `subdev/bios/bit.h`, `subdev/bios/ramcfg.h`, `subdev/bios/M0203.h`.
• Detected declarations: `function files`, `function nvbios_ramcfg_count`, `function nvbios_ramcfg_index`.
• 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.