drivers/soc/fsl/guts.c
Source file repositories/reference/linux-study-clean/drivers/soc/fsl/guts.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/soc/fsl/guts.c- Extension
.c- Size
- 6453 bytes
- Lines
- 274
- 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/io.hlinux/slab.hlinux/module.hlinux/of_fdt.hlinux/sys_soc.hlinux/of_address.hlinux/platform_device.hlinux/fsl/guts.h
Detected Declarations
struct fsl_soc_die_attrstruct fsl_soc_datafunction fsl_guts_get_soc_uidfunction fsl_guts_initmodule init fsl_guts_init
Annotated Snippet
core_initcall(fsl_guts_init);Annotation
- Immediate include surface: `linux/io.h`, `linux/slab.h`, `linux/module.h`, `linux/of_fdt.h`, `linux/sys_soc.h`, `linux/of_address.h`, `linux/platform_device.h`, `linux/fsl/guts.h`.
- Detected declarations: `struct fsl_soc_die_attr`, `struct fsl_soc_data`, `function fsl_guts_get_soc_uid`, `function fsl_guts_init`, `module init fsl_guts_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.