drivers/acpi/battery.c

File Facts

System

Linux kernel

Corpus path

drivers/acpi/battery.c

Extension

.c

Size

38660 bytes

Lines

1338

Domain

Driver Families

Bucket

drivers/acpi

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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/delay.h
• linux/dmi.h
• linux/jiffies.h
• linux/kernel.h
• linux/list.h
• linux/module.h
• linux/mutex.h
• linux/platform_device.h
• linux/slab.h
• linux/suspend.h
• linux/types.h
• linux/unaligned.h
• linux/acpi.h
• linux/power_supply.h
• acpi/battery.h

Detected Declarations

• struct acpi_battery
• struct acpi_offsets
• function acpi_battery_present
• function acpi_battery_technology
• function acpi_battery_is_charged
• function acpi_battery_is_degraded
• function acpi_battery_handle_discharging
• function acpi_battery_get_property
• function extract_package
• function acpi_battery_get_status
• function extract_battery_info
• function acpi_battery_get_info
• function acpi_battery_get_state
• function acpi_battery_set_alarm
• function acpi_battery_init_alarm
• function acpi_battery_alarm_show
• function acpi_battery_alarm_store
• function battery_hook_unregister_unlocked
• function battery_hook_unregister
• function battery_hook_register
• function devm_battery_hook_unregister
• function devm_battery_hook_register
• function battery_hook_add_battery
• function battery_hook_remove_battery
• function battery_hook_exit
• function sysfs_add_battery
• function sysfs_remove_battery
• function find_battery
• function acpi_battery_quirks
• function acpi_battery_update
• function acpi_battery_refresh
• function acpi_battery_notify
• function battery_notify
• function battery_bix_broken_package_quirk
• function battery_notification_delay_quirk
• function battery_ac_is_broken_quirk
• function acpi_battery_wakeup_cleanup
• function devm_acpi_battery_init_wakeup
• function sysfs_battery_cleanup
• function devm_acpi_battery_update_retry
• function acpi_battery_probe
• function acpi_battery_remove
• function acpi_battery_resume
• function acpi_battery_init
• function acpi_battery_exit
• module init acpi_battery_init
• export battery_hook_unregister
• export battery_hook_register

Annotated Snippet

module_init(acpi_battery_init);
module_exit(acpi_battery_exit);

Annotation

• Immediate include surface: `linux/delay.h`, `linux/dmi.h`, `linux/jiffies.h`, `linux/kernel.h`, `linux/list.h`, `linux/module.h`, `linux/mutex.h`, `linux/platform_device.h`.
• Detected declarations: `struct acpi_battery`, `struct acpi_offsets`, `function acpi_battery_present`, `function acpi_battery_technology`, `function acpi_battery_is_charged`, `function acpi_battery_is_degraded`, `function acpi_battery_handle_discharging`, `function acpi_battery_get_property`, `function extract_package`, `function acpi_battery_get_status`.
• Atlas domain: Driver Families / drivers/acpi.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.