drivers/soc/nuvoton/wpcm450-soc.c

File Facts

System

Linux kernel

Corpus path

drivers/soc/nuvoton/wpcm450-soc.c

Extension

.c

Size

2258 bytes

Lines

110

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/of.h
• linux/regmap.h
• linux/slab.h
• linux/sys_soc.h

Detected Declarations

• struct revision
• function get_revision
• function wpcm450_soc_init
• function wpcm450_soc_exit
• module init wpcm450_soc_init

Annotated Snippet

module_init(wpcm450_soc_init);

static void __exit wpcm450_soc_exit(void)
{
	if (wpcm450_soc) {
		soc_device_unregister(wpcm450_soc);
		wpcm450_soc = NULL;
		kfree(wpcm450_attr);
	}
}
module_exit(wpcm450_soc_exit);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Jonathan Neuschäfer");
MODULE_DESCRIPTION("Nuvoton WPCM450 SoC Identification driver");

Annotation

• Immediate include surface: `linux/mfd/syscon.h`, `linux/of.h`, `linux/regmap.h`, `linux/slab.h`, `linux/sys_soc.h`.
• Detected declarations: `struct revision`, `function get_revision`, `function wpcm450_soc_init`, `function wpcm450_soc_exit`, `module init wpcm450_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.