drivers/platform/x86/msi-ec.c

File Facts

System

Linux kernel

Corpus path

drivers/platform/x86/msi-ec.c

Extension

.c

Size

29447 bytes

Lines

1364

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• msi-ec.h
• acpi/battery.h
• linux/acpi.h
• linux/init.h
• linux/kernel.h
• linux/module.h
• linux/platform_device.h
• linux/seq_file.h
• linux/string.h

Detected Declarations

• function ec_read_seq
• function ec_get_firmware_version
• function charge_control_threshold_show
• function charge_control_threshold_store
• function charge_control_start_threshold_show
• function charge_control_start_threshold_store
• function charge_control_end_threshold_show
• function charge_control_end_threshold_store
• function msi_battery_add
• function msi_battery_remove
• function load_configuration
• function msi_ec_init
• function msi_ec_exit
• module init msi_ec_init

Annotated Snippet

module_init(msi_ec_init);
module_exit(msi_ec_exit);

Annotation

• Immediate include surface: `msi-ec.h`, `acpi/battery.h`, `linux/acpi.h`, `linux/init.h`, `linux/kernel.h`, `linux/module.h`, `linux/platform_device.h`, `linux/seq_file.h`.
• Detected declarations: `function ec_read_seq`, `function ec_get_firmware_version`, `function charge_control_threshold_show`, `function charge_control_threshold_store`, `function charge_control_start_threshold_show`, `function charge_control_start_threshold_store`, `function charge_control_end_threshold_show`, `function charge_control_end_threshold_store`, `function msi_battery_add`, `function msi_battery_remove`.
• Atlas domain: Driver Families / drivers/platform.
• Implementation status: integration implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.