drivers/edac/layerscape_edac.c

File Facts

System

Linux kernel

Corpus path

drivers/edac/layerscape_edac.c

Extension

.c

Size

1822 bytes

Lines

78

Domain

Driver Families

Bucket

drivers/edac

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

• edac_module.h
• fsl_ddr_edac.h

Detected Declarations

• function fsl_ddr_mc_init
• function fsl_ddr_mc_exit
• module init fsl_ddr_mc_init

Annotated Snippet

module_init(fsl_ddr_mc_init);

static void __exit fsl_ddr_mc_exit(void)
{
	platform_driver_unregister(&fsl_ddr_mc_err_driver);
}

module_exit(fsl_ddr_mc_exit);

MODULE_DESCRIPTION("Freescale Layerscape EDAC driver");
MODULE_LICENSE("GPL");
MODULE_AUTHOR("NXP Semiconductor");
module_param(edac_op_state, int, 0444);
MODULE_PARM_DESC(edac_op_state, "EDAC Error Reporting state: 0=Poll, 2=Interrupt");

Annotation

• Immediate include surface: `edac_module.h`, `fsl_ddr_edac.h`.
• Detected declarations: `function fsl_ddr_mc_init`, `function fsl_ddr_mc_exit`, `module init fsl_ddr_mc_init`.
• Atlas domain: Driver Families / drivers/edac.
• 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.