drivers/gpu/drm/amd/display/dc/hwss/dce100/dce100_hwseq.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/display/dc/hwss/dce100/dce100_hwseq.h

Extension

.h

Size

1835 bytes

Lines

55

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

• core_types.h
• hw_sequencer_private.h

Detected Declarations

• struct dc
• struct dc_state

Annotated Snippet

#ifndef __DC_HWSS_DCE100_H__
#define __DC_HWSS_DCE100_H__

#include "core_types.h"
#include "hw_sequencer_private.h"

struct dc;
struct dc_state;

void dce100_hw_sequencer_construct(struct dc *dc);

void dce100_prepare_bandwidth(
		struct dc *dc,
		struct dc_state *context);

void dce100_optimize_bandwidth(
		struct dc *dc,
		struct dc_state *context);

bool dce100_enable_display_power_gating(struct dc *dc, uint8_t controller_id,
					struct dc_bios *dcb,
					enum pipe_gating_control power_gating);

void dce100_reset_surface_dcc_and_tiling(struct pipe_ctx *pipe_ctx,
					struct dc_plane_state *plane_state,
					bool clear_tiling);

#endif /* __DC_HWSS_DCE100_H__ */

Annotation

• Immediate include surface: `core_types.h`, `hw_sequencer_private.h`.
• Detected declarations: `struct dc`, `struct dc_state`.
• 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.