drivers/gpu/drm/amd/pm/powerplay/hwmgr/common_baco.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/pm/powerplay/hwmgr/common_baco.h

Extension

.h

Size

1978 bytes

Lines

64

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

• hwmgr.h

Detected Declarations

• struct baco_cmd_entry
• struct soc15_baco_cmd_entry
• enum baco_cmd_type

Annotated Snippet

struct baco_cmd_entry {
	enum baco_cmd_type cmd;
	uint32_t 	reg_offset;
	uint32_t     	mask;
	uint32_t     	shift;
	uint32_t     	timeout;
	uint32_t     	val;
};

struct soc15_baco_cmd_entry {
	enum baco_cmd_type cmd;
	uint32_t 	hwip;
	uint32_t 	inst;
	uint32_t 	seg;
	uint32_t 	reg_offset;
	uint32_t     	mask;
	uint32_t     	shift;
	uint32_t     	timeout;
	uint32_t     	val;
};

extern bool baco_program_registers(struct pp_hwmgr *hwmgr,
				   const struct baco_cmd_entry *entry,
				   const u32 array_size);
extern bool soc15_baco_program_registers(struct pp_hwmgr *hwmgr,
					const struct soc15_baco_cmd_entry *entry,
					const u32 array_size);
#endif

Annotation

• Immediate include surface: `hwmgr.h`.
• Detected declarations: `struct baco_cmd_entry`, `struct soc15_baco_cmd_entry`, `enum baco_cmd_type`.
• 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.