arch/sh/drivers/dma/dma-pvr2.c
Source file repositories/reference/linux-study-clean/arch/sh/drivers/dma/dma-pvr2.c
File Facts
- System
- Linux kernel
- Corpus path
arch/sh/drivers/dma/dma-pvr2.c- Extension
.c- Size
- 2272 bytes
- Lines
- 103
- Domain
- Architecture Layer
- Bucket
- arch/sh
- 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/init.hlinux/kernel.hlinux/module.hlinux/interrupt.hmach/sysasic.hmach/dma.hasm/dma.hasm/io.h
Detected Declarations
function pvr2_dma_interruptfunction pvr2_request_dmafunction pvr2_get_dma_residuefunction pvr2_xfer_dmafunction pvr2_dma_initfunction pvr2_dma_exitmodule init pvr2_dma_init
Annotated Snippet
subsys_initcall(pvr2_dma_init);
module_exit(pvr2_dma_exit);
MODULE_AUTHOR("Paul Mundt <lethal@linux-sh.org>");
MODULE_DESCRIPTION("NEC PowerVR 2 DMA driver");
MODULE_LICENSE("GPL v2");Annotation
- Immediate include surface: `linux/init.h`, `linux/kernel.h`, `linux/module.h`, `linux/interrupt.h`, `mach/sysasic.h`, `mach/dma.h`, `asm/dma.h`, `asm/io.h`.
- Detected declarations: `function pvr2_dma_interrupt`, `function pvr2_request_dma`, `function pvr2_get_dma_residue`, `function pvr2_xfer_dma`, `function pvr2_dma_init`, `function pvr2_dma_exit`, `module init pvr2_dma_init`.
- Atlas domain: Architecture Layer / arch/sh.
- 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.