drivers/gpu/drm/xe/xe_oa.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/xe/xe_oa.h

Extension

.h

Size

681 bytes

Lines

26

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

• xe_oa_types.h

Detected Declarations

• struct drm_device
• struct drm_file
• struct xe_device
• struct xe_gt
• struct xe_hw_engine

Annotated Snippet

#ifndef _XE_OA_H_
#define _XE_OA_H_

#include "xe_oa_types.h"

struct drm_device;
struct drm_file;
struct xe_device;
struct xe_gt;
struct xe_hw_engine;

int xe_oa_init(struct xe_device *xe);
int xe_oa_register(struct xe_device *xe);
int xe_oa_stream_open_ioctl(struct drm_device *dev, u64 data, struct drm_file *file);
int xe_oa_add_config_ioctl(struct drm_device *dev, u64 data, struct drm_file *file);
int xe_oa_remove_config_ioctl(struct drm_device *dev, u64 data, struct drm_file *file);
u32 xe_oa_timestamp_frequency(struct xe_gt *gt);
u16 xe_oa_unit_id(struct xe_hw_engine *hwe);

#endif

Annotation

• Immediate include surface: `xe_oa_types.h`.
• Detected declarations: `struct drm_device`, `struct drm_file`, `struct xe_device`, `struct xe_gt`, `struct xe_hw_engine`.
• 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.