drivers/gpu/drm/i915/display/intel_crt.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/i915/display/intel_crt.h

Extension

.h

Size

761 bytes

Lines

35

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

• intel_display_reg_defs.h

Detected Declarations

• struct drm_encoder
• struct intel_display
• enum pipe
• function intel_crt_port_enabled
• function intel_crt_init

Annotated Snippet

#ifndef __INTEL_CRT_H__
#define __INTEL_CRT_H__

#include "intel_display_reg_defs.h"

enum pipe;
struct drm_encoder;
struct intel_display;

#ifdef I915
bool intel_crt_port_enabled(struct intel_display *display,
			    intel_reg_t adpa_reg, enum pipe *pipe);
void intel_crt_init(struct intel_display *display);
void intel_crt_reset(struct drm_encoder *encoder);
#else
static inline bool intel_crt_port_enabled(struct intel_display *display,
					  intel_reg_t adpa_reg, enum pipe *pipe)
{
	return false;
}
static inline void intel_crt_init(struct intel_display *display)
{
}
static inline void intel_crt_reset(struct drm_encoder *encoder)
{
}
#endif

#endif /* __INTEL_CRT_H__ */

Annotation

• Immediate include surface: `intel_display_reg_defs.h`.
• Detected declarations: `struct drm_encoder`, `struct intel_display`, `enum pipe`, `function intel_crt_port_enabled`, `function intel_crt_init`.
• 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.