drivers/gpu/drm/amd/display/dc/sspl/spl_custom_float.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/display/dc/sspl/spl_custom_float.h

Extension

.h

Size

592 bytes

Lines

30

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

• spl_os_types.h
• spl_fixpt31_32.h

Detected Declarations

• struct spl_custom_float_format
• struct spl_custom_float_value

Annotated Snippet

struct spl_custom_float_format {
	uint32_t mantissa_bits;
	uint32_t exponenta_bits;
	bool sign;
};

struct spl_custom_float_value {
	uint32_t mantissa;
	uint32_t exponenta;
	uint32_t value;
	bool negative;
};

bool SPL_NAMESPACE(spl_convert_to_custom_float_format(
	struct spl_fixed31_32 value,
	const struct spl_custom_float_format *format,
	uint32_t *result));

#endif //SPL_CUSTOM_FLOAT_H_

Annotation

• Immediate include surface: `spl_os_types.h`, `spl_fixpt31_32.h`.
• Detected declarations: `struct spl_custom_float_format`, `struct spl_custom_float_value`.
• 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.