arch/mips/include/asm/mach-rc32434/dma_v.h
Source file repositories/reference/linux-study-clean/arch/mips/include/asm/mach-rc32434/dma_v.h
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/include/asm/mach-rc32434/dma_v.h- Extension
.h- Size
- 1215 bytes
- Lines
- 54
- Domain
- Architecture Layer
- Bucket
- arch/mips
- Inferred role
- Architecture Layer: implementation source
- Status
- source 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
asm/mach-rc32434/dma.hasm/mach-rc32434/rc32434.h
Detected Declarations
function rc32434_halt_dmafunction rc32434_start_dmafunction rc32434_chain_dma
Annotated Snippet
if (__raw_readl(&ch->dmas) & DMA_STAT_HALT) {
__raw_writel(0, &ch->dmas);
break;
}
}
}
return timeout ? 0 : 1;
}
static inline void rc32434_start_dma(struct dma_reg *ch, u32 dma_addr)
{
__raw_writel(0, &ch->dmandptr);
__raw_writel(dma_addr, &ch->dmadptr);
}
static inline void rc32434_chain_dma(struct dma_reg *ch, u32 dma_addr)
{
__raw_writel(dma_addr, &ch->dmandptr);
}
#endif /* _ASM_RC32434_DMA_V_H_ */
Annotation
- Immediate include surface: `asm/mach-rc32434/dma.h`, `asm/mach-rc32434/rc32434.h`.
- Detected declarations: `function rc32434_halt_dma`, `function rc32434_start_dma`, `function rc32434_chain_dma`.
- Atlas domain: Architecture Layer / arch/mips.
- Implementation status: source implementation candidate.
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.