arch/sh/drivers/dma/dmabrg.c
Source file repositories/reference/linux-study-clean/arch/sh/drivers/dma/dmabrg.c
File Facts
- System
- Linux kernel
- Corpus path
arch/sh/drivers/dma/dmabrg.c- Extension
.c- Size
- 5287 bytes
- Lines
- 196
- 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.
- 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/interrupt.hlinux/kernel.hlinux/slab.hasm/dma.hasm/dmabrg.hasm/io.h
Detected Declarations
struct dmabrg_handlerfunction dmabrg_call_handlerfunction possiblefunction dmabrg_disable_irqfunction dmabrg_enable_irqfunction dmabrg_request_irqfunction dmabrg_free_irqfunction dmabrg_initmodule init dmabrg_initexport dmabrg_request_irqexport dmabrg_free_irq
Annotated Snippet
subsys_initcall(dmabrg_init);Annotation
- Immediate include surface: `linux/interrupt.h`, `linux/kernel.h`, `linux/slab.h`, `asm/dma.h`, `asm/dmabrg.h`, `asm/io.h`.
- Detected declarations: `struct dmabrg_handler`, `function dmabrg_call_handler`, `function possible`, `function dmabrg_disable_irq`, `function dmabrg_enable_irq`, `function dmabrg_request_irq`, `function dmabrg_free_irq`, `function dmabrg_init`, `module init dmabrg_init`, `export dmabrg_request_irq`.
- 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.