drivers/gpu/drm/omapdrm/omap_irq.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/omapdrm/omap_irq.h

Extension

.h

Size

801 bytes

Lines

30

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 drm_crtc
• struct drm_device
• struct omap_irq_wait

Annotated Snippet

#ifndef __OMAPDRM_IRQ_H__
#define __OMAPDRM_IRQ_H__

#include <linux/types.h>

struct drm_crtc;
struct drm_device;
struct omap_irq_wait;

int omap_irq_enable_vblank(struct drm_crtc *crtc);
int omap_irq_enable_framedone(struct drm_crtc *crtc, bool enable);
void omap_irq_disable_vblank(struct drm_crtc *crtc);
void omap_drm_irq_uninstall(struct drm_device *dev);
int omap_drm_irq_install(struct drm_device *dev);

struct omap_irq_wait *omap_irq_wait_init(struct drm_device *dev,
		u32 irqmask, int count);
int omap_irq_wait(struct drm_device *dev, struct omap_irq_wait *wait,
		unsigned long timeout);

#endif /* __OMAPDRM_IRQ_H__ */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct drm_crtc`, `struct drm_device`, `struct omap_irq_wait`.
• 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.