arch/arm/kernel/tcm.c
Source file repositories/reference/linux-study-clean/arch/arm/kernel/tcm.c
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/kernel/tcm.c- Extension
.c- Size
- 11885 bytes
- Lines
- 436
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/init.hlinux/kernel.hlinux/module.hlinux/stddef.hlinux/ioport.hlinux/genalloc.hlinux/string.hasm/cputype.hasm/mach/map.hasm/page.hasm/system_info.hasm/traps.hasm/tcm.h
Detected Declarations
function tcm_freefunction tcm_dtcm_presentfunction tcm_itcm_presentfunction setup_tcm_bankfunction functionfunction tcm_initfunction setup_tcm_poolmodule init setup_tcm_poolexport tcm_allocexport tcm_freeexport tcm_dtcm_presentexport tcm_itcm_present
Annotated Snippet
core_initcall(setup_tcm_pool);Annotation
- Immediate include surface: `linux/init.h`, `linux/kernel.h`, `linux/module.h`, `linux/stddef.h`, `linux/ioport.h`, `linux/genalloc.h`, `linux/string.h`, `asm/cputype.h`.
- Detected declarations: `function tcm_free`, `function tcm_dtcm_present`, `function tcm_itcm_present`, `function setup_tcm_bank`, `function function`, `function tcm_init`, `function setup_tcm_pool`, `module init setup_tcm_pool`, `export tcm_alloc`, `export tcm_free`.
- Atlas domain: Architecture Layer / arch/arm.
- Implementation status: integration 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.