drivers/gpu/drm/radeon/radeon_drv.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/radeon/radeon_drv.h

Extension

.h

Size

6000 bytes

Lines

139

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

• linux/firmware.h
• linux/platform_device.h
• radeon_family.h

Detected Declarations

• function radeon_register_atpx_handler
• function radeon_is_atpx_hybrid

Annotated Snippet

static inline void radeon_register_atpx_handler(void) {}
static inline void radeon_unregister_atpx_handler(void) {}
static inline bool radeon_has_atpx_dgpu_power_cntl(void) { return false; }
static inline bool radeon_is_atpx_hybrid(void) { return false; }
#endif

#endif				/* __RADEON_DRV_H__ */

Annotation

• Immediate include surface: `linux/firmware.h`, `linux/platform_device.h`, `radeon_family.h`.
• Detected declarations: `function radeon_register_atpx_handler`, `function radeon_is_atpx_hybrid`.
• 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.