drivers/mtd/ubi/nvmem.c

File Facts

System

Linux kernel

Corpus path

drivers/mtd/ubi/nvmem.c

Extension

.c

Size

4035 bytes

Lines

192

Domain

Driver Families

Bucket

drivers/mtd

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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

• ubi.h
• linux/nvmem-provider.h

Detected Declarations

• struct ubi_nvmem
• function ubi_nvmem_reg_read
• function ubi_nvmem_add
• function ubi_nvmem_remove
• function nvmem_notify
• function ubi_nvmem_init
• function ubi_nvmem_exit
• module init ubi_nvmem_init

Annotated Snippet

module_init(ubi_nvmem_init);
module_exit(ubi_nvmem_exit);
MODULE_DESCRIPTION("NVMEM layer over UBI volumes");
MODULE_AUTHOR("Daniel Golle");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `ubi.h`, `linux/nvmem-provider.h`.
• Detected declarations: `struct ubi_nvmem`, `function ubi_nvmem_reg_read`, `function ubi_nvmem_add`, `function ubi_nvmem_remove`, `function nvmem_notify`, `function ubi_nvmem_init`, `function ubi_nvmem_exit`, `module init ubi_nvmem_init`.
• Atlas domain: Driver Families / drivers/mtd.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.