drivers/soc/versatile/soc-integrator.c
Source file repositories/reference/linux-study-clean/drivers/soc/versatile/soc-integrator.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/soc/versatile/soc-integrator.c- Extension
.c- Size
- 3439 bytes
- Lines
- 151
- Domain
- Driver Families
- Bucket
- drivers/soc
- Inferred role
- Driver Families: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- 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/init.hlinux/io.hlinux/slab.hlinux/sys_soc.hlinux/platform_device.hlinux/mfd/syscon.hlinux/regmap.hlinux/of.h
Detected Declarations
function manufacturer_showfunction arch_showfunction fpga_showfunction build_showfunction integrator_soc_initmodule init integrator_soc_init
Annotated Snippet
device_initcall(integrator_soc_init);Annotation
- Immediate include surface: `linux/init.h`, `linux/io.h`, `linux/slab.h`, `linux/sys_soc.h`, `linux/platform_device.h`, `linux/mfd/syscon.h`, `linux/regmap.h`, `linux/of.h`.
- Detected declarations: `function manufacturer_show`, `function arch_show`, `function fpga_show`, `function build_show`, `function integrator_soc_init`, `module init integrator_soc_init`.
- Atlas domain: Driver Families / drivers/soc.
- 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.