drivers/dma/mcf-edma-main.c

File Facts

System

Linux kernel

Corpus path

drivers/dma/mcf-edma-main.c

Extension

.c

Size

7669 bytes

Lines

300

Domain

Driver Families

Bucket

drivers/dma

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/interrupt.h
• linux/dmaengine.h
• linux/platform_device.h
• linux/platform_data/dma-mcf-edma.h
• fsl-edma-common.h

Detected Declarations

• function mcf_edma_tx_handler
• function mcf_edma_err_handler
• function mcf_edma_irq_init
• function mcf_edma_irq_free
• function mcf_edma_probe
• function mcf_edma_remove
• function mcf_edma_filter_fn
• function mcf_edma_init
• function mcf_edma_exit
• module init mcf_edma_init
• export mcf_edma_filter_fn

Annotated Snippet

subsys_initcall(mcf_edma_init);

static void __exit mcf_edma_exit(void)
{
	platform_driver_unregister(&mcf_edma_driver);
}
module_exit(mcf_edma_exit);

MODULE_ALIAS("platform:mcf-edma");
MODULE_DESCRIPTION("Freescale eDMA engine driver, ColdFire family");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/module.h`, `linux/interrupt.h`, `linux/dmaengine.h`, `linux/platform_device.h`, `linux/platform_data/dma-mcf-edma.h`, `fsl-edma-common.h`.
• Detected declarations: `function mcf_edma_tx_handler`, `function mcf_edma_err_handler`, `function mcf_edma_irq_init`, `function mcf_edma_irq_free`, `function mcf_edma_probe`, `function mcf_edma_remove`, `function mcf_edma_filter_fn`, `function mcf_edma_init`, `function mcf_edma_exit`, `module init mcf_edma_init`.
• Atlas domain: Driver Families / drivers/dma.
• Implementation status: integration 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.