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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

1903 bytes

Lines

51

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct pp_hwmgr
• struct pp_power_state
• struct pp_hw_power_state

Annotated Snippet

#ifndef PROCESSPPTABLES_H
#define PROCESSPPTABLES_H

struct pp_hwmgr;
struct pp_power_state;
struct pp_hw_power_state;

extern const struct pp_table_func pptable_funcs;

typedef int (*pp_tables_hw_clock_info_callback)(struct pp_hwmgr *hwmgr,
						struct pp_hw_power_state *hw_ps,
						unsigned int index,
						const void *clock_info);

int pp_tables_get_num_of_entries(struct pp_hwmgr *hwmgr,
				 unsigned long *num_of_entries);

int pp_tables_get_entry(struct pp_hwmgr *hwmgr,
			unsigned long entry_index,
			struct pp_power_state *ps,
			pp_tables_hw_clock_info_callback func);

int pp_tables_get_response_times(struct pp_hwmgr *hwmgr,
				 uint32_t *vol_rep_time, uint32_t *bb_rep_time);

#endif

Annotation

• Detected declarations: `struct pp_hwmgr`, `struct pp_power_state`, `struct pp_hw_power_state`.
• 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.