drivers/gpu/drm/amd/display/dc/resource/dcn10/dcn10_resource.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/display/dc/resource/dcn10/dcn10_resource.h

Extension

.h

Size

2074 bytes

Lines

60

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
• dml/dcn10/dcn10_fpu.h

Detected Declarations

• struct dc
• struct resource_pool
• struct _vcs_dpi_display_pipe_params_st
• struct dcn10_resource_pool

Annotated Snippet

struct dcn10_resource_pool {
	struct resource_pool base;
};
struct resource_pool *dcn10_create_resource_pool(
		const struct dc_init_data *init_data,
		struct dc *dc);

struct stream_encoder *dcn10_find_first_free_match_stream_enc_for_link(
		struct resource_context *res_ctx,
		const struct resource_pool *pool,
		struct dc_stream_state *stream);

unsigned int dcn10_get_vstartup_for_pipe(struct pipe_ctx *pipe_ctx);

void dcn10_get_default_tiling_info(struct dc_tiling_info *tiling_info);

#endif /* __DC_RESOURCE_DCN10_H__ */

Annotation

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