drivers/power/supply/bq27xxx_battery_hdq.c

File Facts

System

Linux kernel

Corpus path

drivers/power/supply/bq27xxx_battery_hdq.c

Extension

.c

Size

2905 bytes

Lines

129

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.
• 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/kernel.h
• linux/module.h
• linux/device.h
• linux/types.h
• linux/platform_device.h
• linux/mutex.h
• linux/power/bq27xxx_battery.h
• linux/w1.h

Detected Declarations

• function w1_bq27000_read
• function bq27xxx_battery_hdq_read
• function bq27xxx_battery_hdq_add_slave
• function bq27xxx_battery_hdq_remove_slave
• function bq27xxx_battery_hdq_init
• function bq27xxx_battery_hdq_exit
• module init bq27xxx_battery_hdq_init

Annotated Snippet

module_init(bq27xxx_battery_hdq_init);

static void __exit bq27xxx_battery_hdq_exit(void)
{
	w1_unregister_family(&bq27xxx_battery_hdq_family);
}
module_exit(bq27xxx_battery_hdq_exit);

MODULE_AUTHOR("Texas Instruments Ltd");
MODULE_DESCRIPTION("BQ27xxx battery monitor HDQ/1-wire driver");
MODULE_LICENSE("GPL");
MODULE_ALIAS("w1-family-" __stringify(W1_FAMILY_BQ27000));

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/device.h`, `linux/types.h`, `linux/platform_device.h`, `linux/mutex.h`, `linux/power/bq27xxx_battery.h`, `linux/w1.h`.
• Detected declarations: `function w1_bq27000_read`, `function bq27xxx_battery_hdq_read`, `function bq27xxx_battery_hdq_add_slave`, `function bq27xxx_battery_hdq_remove_slave`, `function bq27xxx_battery_hdq_init`, `function bq27xxx_battery_hdq_exit`, `module init bq27xxx_battery_hdq_init`.
• Atlas domain: Driver Families / drivers/power.
• 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.