drivers/gpu/drm/sti/sti_crtc.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/sti/sti_crtc.h

Extension

.h

Size

590 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 drm_crtc
• struct drm_device
• struct drm_plane
• struct notifier_block
• struct sti_mixer

Annotated Snippet

#ifndef _STI_CRTC_H_
#define _STI_CRTC_H_

struct drm_crtc;
struct drm_device;
struct drm_plane;
struct notifier_block;
struct sti_mixer;

int sti_crtc_init(struct drm_device *drm_dev, struct sti_mixer *mixer,
		  struct drm_plane *primary, struct drm_plane *cursor);
int sti_crtc_vblank_cb(struct notifier_block *nb,
		       unsigned long event, void *data);
bool sti_crtc_is_main(struct drm_crtc *drm_crtc);

#endif

Annotation

• Detected declarations: `struct drm_crtc`, `struct drm_device`, `struct drm_plane`, `struct notifier_block`, `struct sti_mixer`.
• 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.