drivers/mtd/devices/ms02-nv.c
Source file repositories/reference/linux-study-clean/drivers/mtd/devices/ms02-nv.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/mtd/devices/ms02-nv.c- Extension
.c- Size
- 7049 bytes
- Lines
- 307
- 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.
- 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/init.hlinux/ioport.hlinux/kernel.hlinux/module.hlinux/mtd/mtd.hlinux/slab.hlinux/types.hasm/addrspace.hasm/bootinfo.hasm/dec/ioasic_addrs.hasm/dec/kn02.hasm/dec/kn03.hasm/io.hasm/paccess.hms02-nv.h
Detected Declarations
function ms02nv_readfunction ms02nv_writefunction ms02nv_probe_onefunction ms02nv_init_onefunction ms02nv_remove_onefunction ms02nv_initfunction ms02nv_cleanupmodule init ms02nv_init
Annotated Snippet
module_init(ms02nv_init);
module_exit(ms02nv_cleanup);Annotation
- Immediate include surface: `linux/init.h`, `linux/ioport.h`, `linux/kernel.h`, `linux/module.h`, `linux/mtd/mtd.h`, `linux/slab.h`, `linux/types.h`, `asm/addrspace.h`.
- Detected declarations: `function ms02nv_read`, `function ms02nv_write`, `function ms02nv_probe_one`, `function ms02nv_init_one`, `function ms02nv_remove_one`, `function ms02nv_init`, `function ms02nv_cleanup`, `module init ms02nv_init`.
- Atlas domain: Driver Families / drivers/mtd.
- 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.