arch/sh/drivers/dma/dma-g2.c

File Facts

System

Linux kernel

Corpus path

arch/sh/drivers/dma/dma-g2.c

Extension

.c

Size

4649 bytes

Lines

198

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.h
• linux/kernel.h
• linux/module.h
• linux/interrupt.h
• asm/cacheflush.h
• mach/sysasic.h
• mach/dma.h
• asm/dma.h

Detected Declarations

• struct g2_channel
• struct g2_status
• struct g2_dma_info
• function g2_dma_interrupt
• function g2_enable_dma
• function g2_disable_dma
• function g2_xfer_dma
• function g2_get_residue
• function g2_dma_init
• function g2_dma_exit
• module init g2_dma_init

Annotated Snippet

subsys_initcall(g2_dma_init);
module_exit(g2_dma_exit);

MODULE_AUTHOR("Paul Mundt <lethal@linux-sh.org>");
MODULE_DESCRIPTION("G2 bus DMA driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/init.h`, `linux/kernel.h`, `linux/module.h`, `linux/interrupt.h`, `asm/cacheflush.h`, `mach/sysasic.h`, `mach/dma.h`, `asm/dma.h`.
• Detected declarations: `struct g2_channel`, `struct g2_status`, `struct g2_dma_info`, `function g2_dma_interrupt`, `function g2_enable_dma`, `function g2_disable_dma`, `function g2_xfer_dma`, `function g2_get_residue`, `function g2_dma_init`, `function g2_dma_exit`.
• 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.