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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

709 bytes

Lines

32

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct intel_crtc_state
• struct intel_display
• struct intel_dsi
• enum port
• function vlv_dsi_wait_for_fifo_empty
• function vlv_dsi_init

Annotated Snippet

#ifndef __VLV_DSI_H__
#define __VLV_DSI_H__

enum port;
struct intel_crtc_state;
struct intel_display;
struct intel_dsi;

#ifdef I915
void vlv_dsi_wait_for_fifo_empty(struct intel_dsi *intel_dsi, enum port port);
int vlv_dsi_min_cdclk(const struct intel_crtc_state *crtc_state);
void vlv_dsi_init(struct intel_display *display);
#else
static inline void vlv_dsi_wait_for_fifo_empty(struct intel_dsi *intel_dsi, enum port port)
{
}
static inline int vlv_dsi_min_cdclk(const struct intel_crtc_state *crtc_state)
{
	return 0;
}
static inline void vlv_dsi_init(struct intel_display *display)
{
}
#endif

#endif /* __VLV_DSI_H__ */

Annotation

• Detected declarations: `struct intel_crtc_state`, `struct intel_display`, `struct intel_dsi`, `enum port`, `function vlv_dsi_wait_for_fifo_empty`, `function vlv_dsi_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.