drivers/mtd/maps/tsunami_flash.c

File Facts

System

Linux kernel

Corpus path

drivers/mtd/maps/tsunami_flash.c

Extension

.c

Size

2550 bytes

Lines

110

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

Dependency Surface

• asm/io.h
• asm/core_tsunami.h
• linux/init.h
• linux/mtd/map.h
• linux/mtd/mtd.h

Detected Declarations

• function tsunami_flash_read8
• function tsunami_flash_write8
• function tsunami_flash_copy_from
• function tsunami_flash_copy_to
• function cleanup_tsunami_flash
• function init_tsunami_flash
• module init init_tsunami_flash

Annotated Snippet

module_init(init_tsunami_flash);
module_exit(cleanup_tsunami_flash);

Annotation

• Immediate include surface: `asm/io.h`, `asm/core_tsunami.h`, `linux/init.h`, `linux/mtd/map.h`, `linux/mtd/mtd.h`.
• Detected declarations: `function tsunami_flash_read8`, `function tsunami_flash_write8`, `function tsunami_flash_copy_from`, `function tsunami_flash_copy_to`, `function cleanup_tsunami_flash`, `function init_tsunami_flash`, `module init init_tsunami_flash`.
• 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.