drivers/mtd/maps/physmap-versatile.h

File Facts

System

Linux kernel

Corpus path

drivers/mtd/maps/physmap-versatile.h

Extension

.h

Size

410 bytes

Lines

18

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/of.h
• linux/mtd/map.h

Detected Declarations

• function of_flash_probe_versatile

Annotated Snippet

#include <linux/of.h>
#include <linux/mtd/map.h>

#ifdef CONFIG_MTD_PHYSMAP_VERSATILE
int of_flash_probe_versatile(struct platform_device *pdev,
			     struct device_node *np,
			     struct map_info *map);
#else
static inline
int of_flash_probe_versatile(struct platform_device *pdev,
			     struct device_node *np,
			     struct map_info *map)
{
	return 0;
}
#endif

Annotation

• Immediate include surface: `linux/of.h`, `linux/mtd/map.h`.
• Detected declarations: `function of_flash_probe_versatile`.
• 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.