drivers/gpu/drm/amd/display/dc/resource/dcn21/dcn21_resource.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/display/dc/resource/dcn21/dcn21_resource.h

Extension

.h

Size

1950 bytes

Lines

58

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

• core_types.h

Detected Declarations

• struct dc
• struct resource_pool
• struct _vcs_dpi_display_pipe_params_st
• struct dcn21_resource_pool

Annotated Snippet

struct dcn21_resource_pool {
	struct resource_pool base;
};
struct resource_pool *dcn21_create_resource_pool(
		const struct dc_init_data *init_data,
		struct dc *dc);
bool dcn21_fast_validate_bw(
		struct dc *dc,
		struct dc_state *context,
		display_e2e_pipe_params_st *pipes,
		int *pipe_cnt_out,
		int *pipe_split_from,
		int *vlevel_out,
		enum dc_validate_mode validate_mode,
		bool allow_self_refresh_only);

#endif /* _DCN21_RESOURCE_H_ */

Annotation

• Immediate include surface: `core_types.h`.
• Detected declarations: `struct dc`, `struct resource_pool`, `struct _vcs_dpi_display_pipe_params_st`, `struct dcn21_resource_pool`.
• 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.