drivers/dma/txx9dmac.c
Source file repositories/reference/linux-study-clean/drivers/dma/txx9dmac.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/dma/txx9dmac.c- Extension
.c- Size
- 34307 bytes
- Lines
- 1305
- 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/dma-mapping.hlinux/init.hlinux/interrupt.hlinux/io.hlinux/module.hlinux/platform_device.hlinux/slab.hlinux/scatterlist.hdmaengine.htxx9dmac.h
Detected Declarations
function Copyrightfunction channel64_readlfunction channel64_write_CHARfunction channel64_clear_CHARfunction channel_read_CHARfunction channel_write_CHARfunction txd_to_txx9dmac_descfunction desc_read_CHARfunction desc_write_CHARfunction txx9dmac_sync_desc_for_cpufunction txx9dmac_desc_putfunction txx9dmac_dump_regsfunction txx9dmac_reset_chanfunction txx9dmac_dostartfunction txx9dmac_descriptor_completefunction txx9dmac_dequeuefunction txx9dmac_complete_allfunction txx9dmac_dump_descfunction txx9dmac_handle_errorfunction txx9dmac_scan_descriptorsfunction list_for_each_entry_safefunction list_for_each_entryfunction txx9dmac_chan_taskletfunction txx9dmac_chan_interruptfunction txx9dmac_taskletfunction txx9dmac_interruptfunction txx9dmac_tx_submitfunction txx9dmac_prep_dma_memcpyfunction txx9dmac_prep_slave_sgfunction for_each_sgfunction txx9dmac_terminate_allfunction txx9dmac_tx_statusfunction txx9dmac_chain_dynamicfunction txx9dmac_issue_pendingfunction txx9dmac_alloc_chan_resourcesfunction txx9dmac_free_chan_resourcesfunction list_for_each_entry_safefunction txx9dmac_offfunction txx9dmac_chan_probefunction txx9dmac_chan_removefunction txx9dmac_probefunction txx9dmac_removefunction txx9dmac_shutdownfunction txx9dmac_suspend_noirqfunction txx9dmac_resume_noirqfunction txx9dmac_initfunction txx9dmac_exitmodule init txx9dmac_init
Annotated Snippet
module_init(txx9dmac_init);
static void __exit txx9dmac_exit(void)
{
platform_driver_unregister(&txx9dmac_chan_driver);
platform_driver_unregister(&txx9dmac_driver);
}
module_exit(txx9dmac_exit);
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("TXx9 DMA Controller driver");
MODULE_AUTHOR("Atsushi Nemoto <anemo@mba.ocn.ne.jp>");
MODULE_ALIAS("platform:txx9dmac");
MODULE_ALIAS("platform:txx9dmac-chan");
Annotation
- Immediate include surface: `linux/dma-mapping.h`, `linux/init.h`, `linux/interrupt.h`, `linux/io.h`, `linux/module.h`, `linux/platform_device.h`, `linux/slab.h`, `linux/scatterlist.h`.
- Detected declarations: `function Copyright`, `function channel64_readl`, `function channel64_write_CHAR`, `function channel64_clear_CHAR`, `function channel_read_CHAR`, `function channel_write_CHAR`, `function txd_to_txx9dmac_desc`, `function desc_read_CHAR`, `function desc_write_CHAR`, `function txx9dmac_sync_desc_for_cpu`.
- 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.