drivers/gpu/drm/amd/display/amdgpu_dm/dc_fpu.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/display/amdgpu_dm/dc_fpu.h

Extension

.h

Size

2073 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.

Dependency Surface

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

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef __DC_FPU_H__
#define __DC_FPU_H__

void dc_assert_fp_enabled(void);
bool dc_is_fp_enabled(void);
void dc_fpu_begin(const char *function_name, const int line);
void dc_fpu_end(const char *function_name, const int line);

#ifndef _LINUX_FPU_COMPILATION_UNIT
#define DC_FP_START()	dc_fpu_begin(__func__, __LINE__)
#define DC_FP_END()	dc_fpu_end(__func__, __LINE__)
#ifdef CONFIG_DRM_AMD_DC_FP
#define DC_RUN_WITH_PREEMPTION_ENABLED(code) \
	do { \
		bool dc_fp_enabled = dc_is_fp_enabled(); \
		if (dc_fp_enabled) \
			DC_FP_END(); \
		code; \
		if (dc_fp_enabled) \
			DC_FP_START(); \
	} while (0)
#else
#define DC_RUN_WITH_PREEMPTION_ENABLED(code) code
#endif // !CONFIG_DRM_AMD_DC_FP
#else
#define DC_FP_START()	BUILD_BUG()
#define DC_FP_END()	BUILD_BUG()
#define DC_RUN_WITH_PREEMPTION_ENABLED(code) code
#endif // !_LINUX_FPU_COMPILATION_UNIT

#endif /* __DC_FPU_H__ */

Annotation

• 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.