drivers/firmware/smccc/soc_id.c

File Facts

System

Linux kernel

Corpus path

drivers/firmware/smccc/soc_id.c

Extension

.c

Size

5090 bytes

Lines

176

Domain

Driver Families

Bucket

drivers/firmware

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/arm-smccc.h
• linux/bitfield.h
• linux/device.h
• linux/module.h
• linux/kernel.h
• linux/slab.h
• linux/sys_soc.h

Detected Declarations

• function str_fragment_from_reg
• function smccc_soc_init
• function smccc_soc_exit
• module init smccc_soc_init

Annotated Snippet

module_init(smccc_soc_init);

static void __exit smccc_soc_exit(void)
{
	if (soc_dev)
		soc_device_unregister(soc_dev);
	kfree(soc_dev_attr);
}
module_exit(smccc_soc_exit);

Annotation

• Immediate include surface: `linux/arm-smccc.h`, `linux/bitfield.h`, `linux/device.h`, `linux/module.h`, `linux/kernel.h`, `linux/slab.h`, `linux/sys_soc.h`.
• Detected declarations: `function str_fragment_from_reg`, `function smccc_soc_init`, `function smccc_soc_exit`, `module init smccc_soc_init`.
• Atlas domain: Driver Families / drivers/firmware.
• 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.