drivers/soc/ti/k3-socinfo.c

File Facts

System

Linux kernel

Corpus path

drivers/soc/ti/k3-socinfo.c

Extension

.c

Size

6386 bytes

Lines

258

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/mfd/syscon.h
• linux/nvmem-consumer.h
• linux/of.h
• linux/of_address.h
• linux/regmap.h
• linux/platform_device.h
• linux/slab.h
• linux/string.h
• linux/sys_soc.h

Detected Declarations

• function k3_chipinfo_get_gpsw_variant
• function k3_chipinfo_partno_to_names
• function k3_chipinfo_variant_to_sr
• function k3_chipinfo_probe
• function k3_chipinfo_init
• module init k3_chipinfo_init

Annotated Snippet

subsys_initcall(k3_chipinfo_init);

Annotation

• Immediate include surface: `linux/mfd/syscon.h`, `linux/nvmem-consumer.h`, `linux/of.h`, `linux/of_address.h`, `linux/regmap.h`, `linux/platform_device.h`, `linux/slab.h`, `linux/string.h`.
• Detected declarations: `function k3_chipinfo_get_gpsw_variant`, `function k3_chipinfo_partno_to_names`, `function k3_chipinfo_variant_to_sr`, `function k3_chipinfo_probe`, `function k3_chipinfo_init`, `module init k3_chipinfo_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.