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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

480 bytes

Lines

19

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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 intel_crtc_state
• struct intel_atomic_state
• enum intel_output_format

Annotated Snippet

#ifndef __INTEL_CRTC_STATE_DUMP_H__
#define __INTEL_CRTC_STATE_DUMP_H__

struct intel_crtc_state;
struct intel_atomic_state;
enum intel_output_format;

void intel_crtc_state_dump(const struct intel_crtc_state *crtc_state,
			   struct intel_atomic_state *state,
			   const char *context);
const char *intel_output_format_name(enum intel_output_format format);

#endif /* __INTEL_CRTC_STATE_H__ */

Annotation

• Detected declarations: `struct intel_crtc_state`, `struct intel_atomic_state`, `enum intel_output_format`.
• Atlas domain: Driver Families / drivers/gpu.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.