drivers/dax/hmem/device.c

File Facts

System

Linux kernel

Corpus path

drivers/dax/hmem/device.c

Extension

.c

Size

2239 bytes

Lines

104

Domain

Driver Families

Bucket

drivers/dax

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

Dependency Surface

• linux/platform_device.h
• linux/memregion.h
• linux/module.h
• linux/dax.h
• linux/mm.h
• ../bus.h

Detected Declarations

• function walk_hmem_resources
• function hmem_work
• function __hmem_register_resource
• function hmem_register_resource
• function hmem_register_one
• function hmem_init
• module init hmem_init
• export walk_hmem_resources

Annotated Snippet

device_initcall(hmem_init);

Annotation

• Immediate include surface: `linux/platform_device.h`, `linux/memregion.h`, `linux/module.h`, `linux/dax.h`, `linux/mm.h`, `../bus.h`.
• Detected declarations: `function walk_hmem_resources`, `function hmem_work`, `function __hmem_register_resource`, `function hmem_register_resource`, `function hmem_register_one`, `function hmem_init`, `module init hmem_init`, `export walk_hmem_resources`.
• Atlas domain: Driver Families / drivers/dax.
• 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.