drivers/gpu/drm/xen/xen_drm_front_kms.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/xen/xen_drm_front_kms.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/xen/xen_drm_front_kms.h- Extension
.h- Size
- 649 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 xen_drm_front_drm_infostruct xen_drm_front_drm_pipeline
Annotated Snippet
#ifndef __XEN_DRM_FRONT_KMS_H_
#define __XEN_DRM_FRONT_KMS_H_
#include <linux/types.h>
struct xen_drm_front_drm_info;
struct xen_drm_front_drm_pipeline;
int xen_drm_front_kms_init(struct xen_drm_front_drm_info *drm_info);
void xen_drm_front_kms_fini(struct xen_drm_front_drm_info *drm_info);
void xen_drm_front_kms_on_frame_done(struct xen_drm_front_drm_pipeline *pipeline,
u64 fb_cookie);
#endif /* __XEN_DRM_FRONT_KMS_H_ */
Annotation
- Immediate include surface: `linux/types.h`.
- Detected declarations: `struct xen_drm_front_drm_info`, `struct xen_drm_front_drm_pipeline`.
- 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.