arch/arm/mach-footbridge/dma-isa.c
Source file repositories/reference/linux-study-clean/arch/arm/mach-footbridge/dma-isa.c
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/mach-footbridge/dma-isa.c- Extension
.c- Size
- 5325 bytes
- Lines
- 231
- Domain
- Architecture Layer
- Bucket
- arch/arm
- Inferred role
- Architecture Layer: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/dma-map-ops.hlinux/ioport.hlinux/init.hlinux/dma-mapping.hlinux/io.hasm/dma.hasm/mach/dma.hasm/hardware/dec21285.h
Detected Declarations
function isa_get_dma_residuefunction isa_enable_dmafunction isa_disable_dmafunction isa_dma_initmodule init isa_dma_init
Annotated Snippet
core_initcall(isa_dma_init);Annotation
- Immediate include surface: `linux/dma-map-ops.h`, `linux/ioport.h`, `linux/init.h`, `linux/dma-mapping.h`, `linux/io.h`, `asm/dma.h`, `asm/mach/dma.h`, `asm/hardware/dec21285.h`.
- Detected declarations: `function isa_get_dma_residue`, `function isa_enable_dma`, `function isa_disable_dma`, `function isa_dma_init`, `module init isa_dma_init`.
- Atlas domain: Architecture Layer / arch/arm.
- 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.