drivers/gpu/drm/xe/xe_dep_scheduler.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/xe/xe_dep_scheduler.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/xe/xe_dep_scheduler.h- Extension
.h- Size
- 578 bytes
- Lines
- 27
- 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_sched_entitystruct workqueue_structstruct xe_dep_schedulerstruct xe_device
Annotated Snippet
#ifndef _XE_DEP_SCHEDULER_H_
#define _XE_DEP_SCHEDULER_H_
#include <linux/types.h>
struct drm_sched_entity;
struct workqueue_struct;
struct xe_dep_scheduler;
struct xe_device;
struct xe_dep_scheduler *
xe_dep_scheduler_create(struct xe_device *xe,
struct workqueue_struct *submit_wq,
const char *name, u32 job_limit);
void xe_dep_scheduler_fini(struct xe_dep_scheduler *dep_scheduler);
struct drm_sched_entity *
xe_dep_scheduler_entity(struct xe_dep_scheduler *dep_scheduler);
#endif
Annotation
- Immediate include surface: `linux/types.h`.
- Detected declarations: `struct drm_sched_entity`, `struct workqueue_struct`, `struct xe_dep_scheduler`, `struct xe_device`.
- 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.