drivers/power/supply/pmu_battery.c

File Facts

System

Linux kernel

Corpus path

drivers/power/supply/pmu_battery.c

Extension

.c

Size

5595 bytes

Lines

224

Domain

Driver Families

Bucket

drivers/power

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/module.h
• linux/platform_device.h
• linux/err.h
• linux/power_supply.h
• linux/adb.h
• linux/pmu.h
• linux/slab.h

Detected Declarations

• function pmu_get_ac_prop
• function pmu_bat_get_property
• function pmu_bat_init
• function pmu_bat_exit
• module init pmu_bat_init

Annotated Snippet

module_init(pmu_bat_init);
module_exit(pmu_bat_exit);

MODULE_AUTHOR("David Woodhouse <dwmw2@infradead.org>");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("PMU battery driver");

Annotation

• Immediate include surface: `linux/module.h`, `linux/platform_device.h`, `linux/err.h`, `linux/power_supply.h`, `linux/adb.h`, `linux/pmu.h`, `linux/slab.h`.
• Detected declarations: `function pmu_get_ac_prop`, `function pmu_bat_get_property`, `function pmu_bat_init`, `function pmu_bat_exit`, `module init pmu_bat_init`.
• Atlas domain: Driver Families / drivers/power.
• 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.