drivers/w1/slaves/w1_smem.c

File Facts

System

Linux kernel

Corpus path

drivers/w1/slaves/w1_smem.c

Extension

.c

Size

1247 bytes

Lines

60

Domain

Driver Families

Bucket

drivers/w1

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• asm/types.h
• linux/kernel.h
• linux/module.h
• linux/moduleparam.h
• linux/device.h
• linux/types.h
• linux/w1.h

Detected Declarations

• function w1_smem_init
• function w1_smem_fini
• module init w1_smem_init

Annotated Snippet

module_init(w1_smem_init);
module_exit(w1_smem_fini);

MODULE_AUTHOR("Evgeniy Polyakov <zbr@ioremap.net>");
MODULE_DESCRIPTION("Driver for 1-wire Dallas network protocol, 64bit memory family.");
MODULE_LICENSE("GPL");
MODULE_ALIAS("w1-family-" __stringify(W1_FAMILY_SMEM_01));
MODULE_ALIAS("w1-family-" __stringify(W1_FAMILY_SMEM_81));

Annotation

• Immediate include surface: `asm/types.h`, `linux/kernel.h`, `linux/module.h`, `linux/moduleparam.h`, `linux/device.h`, `linux/types.h`, `linux/w1.h`.
• Detected declarations: `function w1_smem_init`, `function w1_smem_fini`, `module init w1_smem_init`.
• Atlas domain: Driver Families / drivers/w1.
• 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.