drivers/gpu/drm/amd/display/dc/dce60/dce60_timing_generator.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/display/dc/dce60/dce60_timing_generator.h

Extension

.h

Size

1590 bytes

Lines

40

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

• timing_generator.h
• ../include/grph_object_id.h

Detected Declarations

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

Annotated Snippet

#ifndef __DC_TIMING_GENERATOR_DCE60_H__
#define __DC_TIMING_GENERATOR_DCE60_H__

#include "timing_generator.h"
#include "../include/grph_object_id.h"

/* DCE6.0 implementation inherits from DCE11.0 */
void dce60_timing_generator_construct(
	struct dce110_timing_generator *tg,
	struct dc_context *ctx,
	uint32_t instance,
	const struct dce110_timing_generator_offsets *offsets);

#endif /* __DC_TIMING_GENERATOR_DCE60_H__ */

Annotation

• Immediate include surface: `timing_generator.h`, `../include/grph_object_id.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.