drivers/gpu/drm/xe/xe_sriov_pf.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/xe/xe_sriov_pf.h

Extension

.h

Size

1019 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

• linux/types.h

Detected Declarations

• struct dentry
• struct drm_printer
• struct xe_device
• function xe_sriov_pf_readiness
• function xe_sriov_pf_init_early
• function xe_sriov_pf_init_late
• function xe_sriov_pf_lockdown
• function xe_sriov_pf_end_lockdown

Annotated Snippet

static inline bool xe_sriov_pf_readiness(struct xe_device *xe) { return false; }
static inline int xe_sriov_pf_init_early(struct xe_device *xe) { return 0; }
static inline int xe_sriov_pf_init_late(struct xe_device *xe) { return 0; }
static inline int xe_sriov_pf_lockdown(struct xe_device *xe) { return 0; }
static inline void xe_sriov_pf_end_lockdown(struct xe_device *xe) { }
#endif

#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct dentry`, `struct drm_printer`, `struct xe_device`, `function xe_sriov_pf_readiness`, `function xe_sriov_pf_init_early`, `function xe_sriov_pf_init_late`, `function xe_sriov_pf_lockdown`, `function xe_sriov_pf_end_lockdown`.
• 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.