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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

720 bytes

Lines

24

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

• linux/types.h

Detected Declarations

• struct intel_crtc_state
• struct intel_display
• struct intel_dp
• struct link_config_limits

Annotated Snippet

#ifndef __INTEL_DP_TEST_H__
#define __INTEL_DP_TEST_H__

#include <linux/types.h>

struct intel_crtc_state;
struct intel_display;
struct intel_dp;
struct link_config_limits;

void intel_dp_test_reset(struct intel_dp *intel_dp);
void intel_dp_test_request(struct intel_dp *intel_dp);
void intel_dp_test_compute_config(struct intel_dp *intel_dp,
				  struct intel_crtc_state *pipe_config,
				  struct link_config_limits *limits);
bool intel_dp_test_phy(struct intel_dp *intel_dp);
bool intel_dp_test_short_pulse(struct intel_dp *intel_dp);
void intel_dp_test_debugfs_register(struct intel_display *display);

#endif /* __INTEL_DP_TEST_H__ */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct intel_crtc_state`, `struct intel_display`, `struct intel_dp`, `struct link_config_limits`.
• 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.