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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

667 bytes

Lines

22

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_display
• enum pipe
• enum transcoder

Annotated Snippet

#ifndef __INTEL_GVT_API_H__
#define __INTEL_GVT_API_H__

#include <linux/types.h>

enum pipe;
enum transcoder;
struct intel_display;

u32 intel_display_device_pipe_offset(struct intel_display *display, enum pipe pipe);
u32 intel_display_device_trans_offset(struct intel_display *display, enum transcoder trans);
u32 intel_display_device_cursor_offset(struct intel_display *display, enum pipe pipe);
u32 intel_display_device_mmio_base(struct intel_display *display);
bool intel_display_device_pipe_valid(struct intel_display *display, enum pipe pipe);

#endif /* __INTEL_GVT_API_H__ */

Annotation

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