drivers/gpu/drm/xe/xe_module.c
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/xe/xe_module.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/xe/xe_module.c- Extension
.c- Size
- 4832 bytes
- Lines
- 174
- Domain
- Driver Families
- Bucket
- drivers/gpu
- Inferred role
- Driver Families: exported/initcall integration point
- Status
- integration 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.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
xe_module.hlinux/init.hlinux/module.hdrm/drm_module.hxe_defaults.hxe_device_types.hxe_drv.hxe_configfs.hxe_hw_fence.hxe_pci.hxe_pm.hxe_observation.hxe_sched_job.h
Detected Declarations
struct init_funcsfunction xe_check_nomodesetfunction xe_call_init_funcfunction xe_call_exit_funcfunction xe_initfunction xe_exitmodule init xe_init
Annotated Snippet
module_init(xe_init);
module_exit(xe_exit);
MODULE_AUTHOR("Intel Corporation");
MODULE_DESCRIPTION(DRIVER_DESC);
MODULE_LICENSE("GPL and additional rights");Annotation
- Immediate include surface: `xe_module.h`, `linux/init.h`, `linux/module.h`, `drm/drm_module.h`, `xe_defaults.h`, `xe_device_types.h`, `xe_drv.h`, `xe_configfs.h`.
- Detected declarations: `struct init_funcs`, `function xe_check_nomodeset`, `function xe_call_init_func`, `function xe_call_exit_func`, `function xe_init`, `function xe_exit`, `module init xe_init`.
- Atlas domain: Driver Families / drivers/gpu.
- Implementation status: integration 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.