drivers/gpu/drm/amd/display/dc/dml2_0/dml2_wrapper_fpu.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/display/dc/dml2_0/dml2_wrapper_fpu.h

Extension

.h

Size

706 bytes

Lines

26

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

• os_types.h

Detected Declarations

• struct dml2_context
• struct dc
• struct ip_params_st
• struct soc_bounding_box_st
• struct soc_states_st

Annotated Snippet

#ifndef _DML2_WRAPPER_FPU_H_
#define _DML2_WRAPPER_FPU_H_

#include "os_types.h"

struct dml2_context;
struct dc;
struct ip_params_st;
struct soc_bounding_box_st;
struct soc_states_st;

void initialize_dml2_ip_params(struct dml2_context *dml2, const struct dc *in_dc, struct ip_params_st *out);
void initialize_dml2_soc_bbox(struct dml2_context *dml2, const struct dc *in_dc, struct soc_bounding_box_st *out);
void initialize_dml2_soc_states(struct dml2_context *dml2,
	const struct dc *in_dc, const struct soc_bounding_box_st *in_bbox, struct soc_states_st *out);

#endif //_DML2_WRAPPER_FPU_H_

Annotation

• Immediate include surface: `os_types.h`.
• Detected declarations: `struct dml2_context`, `struct dc`, `struct ip_params_st`, `struct soc_bounding_box_st`, `struct soc_states_st`.
• 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.