drivers/gpu/drm/xe/xe_hw_engine_class_sysfs.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/xe/xe_hw_engine_class_sysfs.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/xe/xe_hw_engine_class_sysfs.h- Extension
.h- Size
- 1120 bytes
- Lines
- 44
- 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/kobject.h
Detected Declarations
struct xe_gtstruct xe_hw_engine_class_intfstruct kobj_eclass
Annotated Snippet
struct kobj_eclass {
/** @base: The actual kobject */
struct kobject base;
/** @eclass: A pointer to the hw engine class interface */
struct xe_hw_engine_class_intf *eclass;
/** @xe: A pointer to the xe device */
struct xe_device *xe;
};
static inline struct xe_hw_engine_class_intf *kobj_to_eclass(struct kobject *kobj)
{
return container_of(kobj, struct kobj_eclass, base)->eclass;
}
static inline struct xe_device *kobj_to_xe(struct kobject *kobj)
{
return container_of(kobj, struct kobj_eclass, base)->xe;
}
#endif
Annotation
- Immediate include surface: `linux/kobject.h`.
- Detected declarations: `struct xe_gt`, `struct xe_hw_engine_class_intf`, `struct kobj_eclass`.
- 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.