drivers/gpu/drm/amd/display/dc/clk_mgr/dcn301/vg_clk_mgr.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/display/dc/clk_mgr/dcn301/vg_clk_mgr.h

Extension

.h

Size

1744 bytes

Lines

53

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

• clk_mgr_internal.h

Detected Declarations

• struct watermarks
• struct smu_watermark_set
• struct clk_mgr_vgh

Annotated Snippet

struct smu_watermark_set {
	struct watermarks *wm_set;
	union large_integer mc_address;
};

struct clk_mgr_vgh {
	struct clk_mgr_internal base;
	struct smu_watermark_set smu_wm_set;
};

void vg_clk_mgr_construct(struct dc_context *ctx,
		struct clk_mgr_vgh *clk_mgr,
		struct pp_smu_funcs *pp_smu,
		struct dccg *dccg);

void vg_clk_mgr_destroy(struct clk_mgr_internal *clk_mgr);

#endif //__VG_CLK_MGR_H__

Annotation

• Immediate include surface: `clk_mgr_internal.h`.
• Detected declarations: `struct watermarks`, `struct smu_watermark_set`, `struct clk_mgr_vgh`.
• 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.