drivers/power/supply/ab8500-chargalg.h

File Facts

System

Linux kernel

Corpus path

drivers/power/supply/ab8500-chargalg.h

Extension

.h

Size

1279 bytes

Lines

48

Domain

Driver Families

Bucket

drivers/power

Inferred role

Driver Families: implementation source

Status

source 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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/power_supply.h

Detected Declarations

• struct ux500_charger
• struct ux500_charger_ops
• struct ux500_charger

Annotated Snippet

struct ux500_charger_ops {
	int (*enable) (struct ux500_charger *, int, int, int);
	int (*check_enable) (struct ux500_charger *, int, int);
	int (*kick_wd) (struct ux500_charger *);
	int (*update_curr) (struct ux500_charger *, int);
};

/**
 * struct ux500_charger - power supply ux500 charger sub class
 * @psy			power supply base class
 * @ops			ux500 charger operations
 * @max_out_volt_uv	maximum output charger voltage in uV
 * @max_out_curr_ua	maximum output charger current in uA
 * @enabled		indicates if this charger is used or not
 */
struct ux500_charger {
	struct power_supply *psy;
	struct ux500_charger_ops ops;
	int max_out_volt_uv;
	int max_out_curr_ua;
	int wdt_refresh;
	bool enabled;
};

#endif /* _AB8500_CHARGALG_H_ */

Annotation

• Immediate include surface: `linux/power_supply.h`.
• Detected declarations: `struct ux500_charger`, `struct ux500_charger_ops`, `struct ux500_charger`.
• Atlas domain: Driver Families / drivers/power.
• Implementation status: source 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.