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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

1852 bytes

Lines

44

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

• amdgpu.h
• dc.h
• modules/inc/mod_power.h

Detected Declarations

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

Annotated Snippet

#ifndef AMDGPU_DM_AMDGPU_DM_REPLAY_H_
#define AMDGPU_DM_AMDGPU_DM_REPLAY_H_

#include "amdgpu.h"
#include "dc.h"
#include "modules/inc/mod_power.h"

bool amdgpu_dm_link_supports_replay(struct dc_link *link,
		struct amdgpu_dm_connector *aconnector);
bool amdgpu_dm_set_replay_caps(struct dc_link *link,
		struct amdgpu_dm_connector *aconnector);
bool amdgpu_dm_link_setup_replay(struct dc_stream_state *stream,
		struct mod_vrr_params *vrr_params);
bool amdgpu_dm_replay_set_event(struct amdgpu_display_manager *dm,
		struct dc_stream_state *stream, bool set_event,
		enum replay_event event, bool wait_for_disable);
#endif /* AMDGPU_DM_AMDGPU_DM_REPLAY_H_ */

Annotation

• Immediate include surface: `amdgpu.h`, `dc.h`, `modules/inc/mod_power.h`.
• 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.