drivers/gpu/drm/msm/disp/dpu1/dpu_core_irq.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/msm/disp/dpu1/dpu_core_irq.h

Extension

.h

Size

796 bytes

Lines

35

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• dpu_kms.h
• dpu_hw_interrupts.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef __DPU_CORE_IRQ_H__
#define __DPU_CORE_IRQ_H__

#include "dpu_kms.h"
#include "dpu_hw_interrupts.h"

void dpu_core_irq_preinstall(struct msm_kms *kms);

void dpu_core_irq_uninstall(struct msm_kms *kms);

irqreturn_t dpu_core_irq(struct msm_kms *kms);

u32 dpu_core_irq_read(
		struct dpu_kms *dpu_kms,
		unsigned int irq_idx);

int dpu_core_irq_register_callback(
		struct dpu_kms *dpu_kms,
		unsigned int irq_idx,
		void (*irq_cb)(void *arg),
		void *irq_arg);

int dpu_core_irq_unregister_callback(
		struct dpu_kms *dpu_kms,
		unsigned int irq_idx);

void dpu_debugfs_core_irq_init(struct dpu_kms *dpu_kms,
		struct dentry *parent);

#endif /* __DPU_CORE_IRQ_H__ */

Annotation

• Immediate include surface: `dpu_kms.h`, `dpu_hw_interrupts.h`.
• Atlas domain: Driver Families / drivers/gpu.
• Implementation status: source implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.