drivers/gpu/drm/amd/pm/powerplay/hwmgr/pp_overdriver.c

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/pm/powerplay/hwmgr/pp_overdriver.c

Extension

.c

Size

166080 bytes

Lines

1289

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

• pp_overdriver.h
• linux/errno.h

Detected Declarations

• function pp_override_get_default_fuse_value

Annotated Snippet

if (key == list[i].key) {
			result->key =  list[i].key;
			result->VFT2_m1 = list[i].VFT2_m1;
			result->VFT2_m2 = list[i].VFT2_m2;
			result->VFT2_b  = list[i].VFT2_b;
			result->VFT1_m1 = list[i].VFT1_m1;
			result->VFT1_m2 = list[i].VFT1_m2;
			result->VFT1_b  = list[i].VFT1_b;
			result->VFT0_m1 = list[i].VFT0_m1;
			result->VFT0_m2 = list[i].VFT0_m2;
			result->VFT0_b  = list[i].VFT0_b;
			return 0;
		}
	}

	return -EINVAL;
}

Annotation

• Immediate include surface: `pp_overdriver.h`, `linux/errno.h`.
• Detected declarations: `function pp_override_get_default_fuse_value`.
• 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.