drivers/gpu/drm/radeon/radeon_atombios.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/radeon/radeon_atombios.h

Extension

.h

Size

1869 bytes

Lines

46

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

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

Detected Declarations

• struct drm_connector
• struct drm_device
• struct drm_display_mode
• struct radeon_device
• struct radeon_encoder

Annotated Snippet

#ifndef __RADEON_ATOMBIOS_H__
#define __RADEON_ATOMBIOS_H__

struct drm_connector;
struct drm_device;
struct drm_display_mode;
struct radeon_device;
struct radeon_encoder;

bool radeon_atom_get_tv_timings(struct radeon_device *rdev, int index,
				struct drm_display_mode *mode);
void radeon_add_atom_encoder(struct drm_device *dev, uint32_t encoder_enum,
			     uint32_t supported_device, u16 caps);
void radeon_atom_backlight_init(struct radeon_encoder *radeon_encoder,
				struct drm_connector *drm_connector);


#endif                         /* __RADEON_ATOMBIOS_H__ */

Annotation

• Detected declarations: `struct drm_connector`, `struct drm_device`, `struct drm_display_mode`, `struct radeon_device`, `struct radeon_encoder`.
• 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.