drivers/power/supply/max17042_battery.c

File Facts

System

Linux kernel

Corpus path

drivers/power/supply/max17042_battery.c

Extension

.c

Size

40000 bytes

Lines

1442

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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/devm-helpers.h
• linux/init.h
• linux/module.h
• linux/slab.h
• linux/i2c.h
• linux/delay.h
• linux/interrupt.h
• linux/platform_device.h
• linux/pm.h
• linux/mod_devicetable.h
• linux/power_supply.h
• linux/power/max17042_battery.h
• linux/of.h
• linux/regmap.h

Detected Declarations

• struct max17042_chip
• function max17042_get_temperature
• function max17042_get_status
• function max17042_get_battery_health
• function max17042_get_property
• function max17042_set_property
• function max17042_property_is_writeable
• function max17042_write_verify_reg
• function max17042_override_por
• function max17042_unlock_model
• function max17042_lock_model
• function max17042_write_model_data
• function max17042_read_model_data
• function max17042_model_data_compare
• function max17042_init_model
• function max17042_verify_model_lock
• function max17042_write_config_regs
• function max17042_write_custom_regs
• function max17042_update_capacity_regs
• function max17042_reset_vfsoc0_reg
• function max17042_load_new_capacity_params
• function max17042_override_por_values
• function max17042_init_chip
• function max17042_set_soc_threshold
• function max17042_set_critical_soc_threshold
• function max17042_enable_soc_alerts
• function max17042_suspend_soc_alerts
• function max17042_thread_handler
• function max17042_init_worker
• function max17042_parse_dt
• function max17042_init_defaults
• function max17042_probe
• function max17042_i2c_probe
• function max17042_platform_probe
• function max17042_suspend
• function max17042_resume
• function max17042_init
• function max17042_exit
• module init max17042_init

Annotated Snippet

module_init(max17042_init);

static void __exit max17042_exit(void)
{
	i2c_del_driver(&max17042_i2c_driver);
	platform_driver_unregister(&max17042_platform_driver);
}
module_exit(max17042_exit);

MODULE_AUTHOR("MyungJoo Ham <myungjoo.ham@samsung.com>");
MODULE_DESCRIPTION("MAX17042 Fuel Gauge");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/devm-helpers.h`, `linux/init.h`, `linux/module.h`, `linux/slab.h`, `linux/i2c.h`, `linux/delay.h`, `linux/interrupt.h`.
• Detected declarations: `struct max17042_chip`, `function max17042_get_temperature`, `function max17042_get_status`, `function max17042_get_battery_health`, `function max17042_get_property`, `function max17042_set_property`, `function max17042_property_is_writeable`, `function max17042_write_verify_reg`, `function max17042_override_por`, `function max17042_unlock_model`.
• Atlas domain: Driver Families / drivers/power.
• 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.