drivers/platform/x86/intel/pmc/pltdrv.c

File Facts

System

Linux kernel

Corpus path

drivers/platform/x86/intel/pmc/pltdrv.c

Extension

.c

Size

2698 bytes

Lines

91

Domain

Driver Families

Bucket

drivers/platform

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/acpi.h
• linux/module.h
• linux/platform_device.h
• asm/cpu_device_id.h
• asm/intel-family.h
• xen/xen.h

Detected Declarations

• function Copyright
• function pmc_core_platform_init
• function pmc_core_platform_exit
• module init pmc_core_platform_init

Annotated Snippet

module_init(pmc_core_platform_init);
module_exit(pmc_core_platform_exit);
MODULE_DESCRIPTION("Intel PMC Core platform driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/module.h`, `linux/platform_device.h`, `asm/cpu_device_id.h`, `asm/intel-family.h`, `xen/xen.h`.
• Detected declarations: `function Copyright`, `function pmc_core_platform_init`, `function pmc_core_platform_exit`, `module init pmc_core_platform_init`.
• Atlas domain: Driver Families / drivers/platform.
• 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.