drivers/gpu/drm/xe/display/xe_fb_pin.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/xe/display/xe_fb_pin.h

Extension

.h

Size

535 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 drm_gem_object
• struct i915_vma
• struct intel_fb_pin_params

Annotated Snippet

#ifndef __XE_FB_PIN_H__
#define __XE_FB_PIN_H__

#include <linux/types.h>

struct drm_gem_object;
struct i915_vma;
struct intel_fb_pin_params;

int xe_fb_pin_ggtt_pin(struct drm_gem_object *obj,
		       const struct intel_fb_pin_params *pin_params,
		       struct i915_vma **out_ggtt_vma,
		       u32 *out_offset,
		       int *out_fence_id);

extern const struct intel_display_fb_pin_interface xe_display_fb_pin_interface;

#endif /* __XE_FB_PIN_H__ */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct drm_gem_object`, `struct i915_vma`, `struct intel_fb_pin_params`.
• 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.