drivers/dma/moxart-dma.c

File Facts

System

Linux kernel

Corpus path

drivers/dma/moxart-dma.c

Extension

.c

Size

16078 bytes

Lines

669

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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/dmaengine.h
• linux/dma-mapping.h
• linux/err.h
• linux/init.h
• linux/interrupt.h
• linux/list.h
• linux/module.h
• linux/platform_device.h
• linux/slab.h
• linux/spinlock.h
• linux/of_address.h
• linux/of_irq.h
• linux/of_dma.h
• linux/bitops.h
• asm/cacheflush.h
• dmaengine.h
• virt-dma.h

Detected Declarations

• struct moxart_sg
• struct moxart_desc
• struct moxart_chan
• struct moxart_dmadev
• function moxart_dma_desc_free
• function moxart_terminate_all
• function moxart_slave_config
• function for_each_sg
• function moxart_alloc_chan_resources
• function moxart_free_chan_resources
• function moxart_dma_set_params
• function moxart_set_transfer_params
• function moxart_start_dma
• function moxart_dma_start_sg
• function moxart_dma_start_desc
• function moxart_issue_pending
• function moxart_dma_desc_size
• function moxart_dma_desc_size_in_flight
• function moxart_tx_status
• function moxart_dma_init
• function moxart_dma_interrupt
• function moxart_probe
• function moxart_remove
• function moxart_init
• function moxart_exit
• module init moxart_init

Annotated Snippet

subsys_initcall(moxart_init);

static void __exit moxart_exit(void)
{
	platform_driver_unregister(&moxart_driver);
}
module_exit(moxart_exit);

MODULE_AUTHOR("Jonas Jensen <jonas.jensen@gmail.com>");
MODULE_DESCRIPTION("MOXART DMA engine driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/dmaengine.h`, `linux/dma-mapping.h`, `linux/err.h`, `linux/init.h`, `linux/interrupt.h`, `linux/list.h`, `linux/module.h`, `linux/platform_device.h`.
• Detected declarations: `struct moxart_sg`, `struct moxart_desc`, `struct moxart_chan`, `struct moxart_dmadev`, `function moxart_dma_desc_free`, `function moxart_terminate_all`, `function moxart_slave_config`, `function for_each_sg`, `function moxart_alloc_chan_resources`, `function moxart_free_chan_resources`.
• Atlas domain: Driver Families / drivers/dma.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• 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.