drivers/mtd/parsers/ofpart_linksys_ns.c
Source file repositories/reference/linux-study-clean/drivers/mtd/parsers/ofpart_linksys_ns.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/mtd/parsers/ofpart_linksys_ns.c- Extension
.c- Size
- 1129 bytes
- Lines
- 51
- Domain
- Driver Families
- Bucket
- drivers/mtd
- Inferred role
- Driver Families: implementation source
- Status
- source 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/bcm47xx_nvram.hlinux/mtd/mtd.hlinux/mtd/partitions.hofpart_linksys_ns.h
Detected Declarations
function Copyrightfunction linksys_ns_partitions_post_parse
Annotated Snippet
if (of_device_is_compatible(parts[i].of_node, "linksys,ns-firmware")) {
if (trx_idx++ == bootpartition)
parts[i].name = "firmware";
else
parts[i].name = "backup";
}
}
return 0;
}
Annotation
- Immediate include surface: `linux/bcm47xx_nvram.h`, `linux/mtd/mtd.h`, `linux/mtd/partitions.h`, `ofpart_linksys_ns.h`.
- Detected declarations: `function Copyright`, `function linksys_ns_partitions_post_parse`.
- Atlas domain: Driver Families / drivers/mtd.
- Implementation status: source 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.