drivers/gpu/drm/xe/xe_sysctrl.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/xe/xe_sysctrl.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/xe/xe_sysctrl.h- Extension
.h- Size
- 552 bytes
- Lines
- 25
- 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/container_of.hxe_device_types.hxe_sysctrl_types.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef _XE_SYSCTRL_H_
#define _XE_SYSCTRL_H_
#include <linux/container_of.h>
#include "xe_device_types.h"
#include "xe_sysctrl_types.h"
static inline struct xe_device *sc_to_xe(struct xe_sysctrl *sc)
{
return container_of(sc, struct xe_device, sc);
}
void xe_sysctrl_event(struct xe_sysctrl *sc);
int xe_sysctrl_init(struct xe_device *xe);
void xe_sysctrl_irq_handler(struct xe_device *xe, u32 master_ctl);
void xe_sysctrl_pm_resume(struct xe_device *xe);
#endif
Annotation
- Immediate include surface: `linux/container_of.h`, `xe_device_types.h`, `xe_sysctrl_types.h`.
- 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.