drivers/mcb/mcb-lpc.c

File Facts

System

Linux kernel

Corpus path

drivers/mcb/mcb-lpc.c

Extension

.c

Size

4270 bytes

Lines

188

Domain

Driver Families

Bucket

drivers/mcb

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.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/platform_device.h
• linux/module.h
• linux/dmi.h
• linux/mcb.h
• linux/io.h
• mcb-internal.h

Detected Declarations

• struct priv
• function mcb_lpc_probe
• function mcb_lpc_remove
• function mcb_lpc_create_platform_device
• function mcb_lpc_init
• function mcb_lpc_exit
• module init mcb_lpc_init

Annotated Snippet

module_init(mcb_lpc_init);
module_exit(mcb_lpc_exit);

MODULE_AUTHOR("Andreas Werner <andreas.werner@men.de>");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("MCB over LPC support");
MODULE_IMPORT_NS("MCB");

Annotation

• Immediate include surface: `linux/platform_device.h`, `linux/module.h`, `linux/dmi.h`, `linux/mcb.h`, `linux/io.h`, `mcb-internal.h`.
• Detected declarations: `struct priv`, `function mcb_lpc_probe`, `function mcb_lpc_remove`, `function mcb_lpc_create_platform_device`, `function mcb_lpc_init`, `function mcb_lpc_exit`, `module init mcb_lpc_init`.
• Atlas domain: Driver Families / drivers/mcb.
• 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.