drivers/gpu/drm/i915/display/intel_cursor.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/i915/display/intel_cursor.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/i915/display/intel_cursor.h- Extension
.h- Size
- 442 bytes
- Lines
- 23
- 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
- No C-style include directives detected by the generator.
Detected Declarations
struct intel_displaystruct intel_planestruct kthread_workenum pipe
Annotated Snippet
#ifndef _INTEL_CURSOR_H_
#define _INTEL_CURSOR_H_
enum pipe;
struct intel_display;
struct intel_plane;
struct kthread_work;
struct intel_plane *
intel_cursor_plane_create(struct intel_display *display,
enum pipe pipe);
void intel_cursor_unpin_work(struct kthread_work *base);
void intel_cursor_mode_config_init(struct intel_display *display);
#endif
Annotation
- Detected declarations: `struct intel_display`, `struct intel_plane`, `struct kthread_work`, `enum pipe`.
- 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.