drivers/gpu/drm/tidss/tidss_crtc.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/tidss/tidss_crtc.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/tidss/tidss_crtc.h- Extension
.h- Size
- 1074 bytes
- Lines
- 49
- 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/completion.hlinux/wait.hdrm/drm_crtc.h
Detected Declarations
struct tidss_devicestruct tidss_crtcstruct tidss_crtc_state
Annotated Snippet
struct tidss_crtc {
struct drm_crtc crtc;
u32 hw_videoport;
struct drm_pending_vblank_event *event;
struct completion framedone_completion;
};
#define to_tidss_crtc_state(x) container_of(x, struct tidss_crtc_state, base)
struct tidss_crtc_state {
/* Must be first. */
struct drm_crtc_state base;
bool plane_pos_changed;
u32 bus_format;
u32 bus_flags;
};
void tidss_crtc_vblank_irq(struct drm_crtc *crtc);
void tidss_crtc_framedone_irq(struct drm_crtc *crtc);
void tidss_crtc_error_irq(struct drm_crtc *crtc, u64 irqstatus);
struct tidss_crtc *tidss_crtc_create(struct tidss_device *tidss,
u32 hw_videoport,
struct drm_plane *primary);
#endif
Annotation
- Immediate include surface: `linux/completion.h`, `linux/wait.h`, `drm/drm_crtc.h`.
- Detected declarations: `struct tidss_device`, `struct tidss_crtc`, `struct tidss_crtc_state`.
- 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.