drivers/regulator/da9062-regulator.c

File Facts

System

Linux kernel

Corpus path

drivers/regulator/da9062-regulator.c

Extension

.c

Size

33962 bytes

Lines

1057

Domain

Driver Families

Bucket

drivers/regulator

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/kernel.h
• linux/module.h
• linux/init.h
• linux/err.h
• linux/slab.h
• linux/of.h
• linux/platform_device.h
• linux/regmap.h
• linux/regulator/driver.h
• linux/regulator/machine.h
• linux/regulator/of_regulator.h
• linux/mfd/da9062/core.h
• linux/mfd/da9062/registers.h
• dt-bindings/regulator/dlg,da9063-regulator.h

Detected Declarations

• struct da9062_regulator_info
• struct da9062_regulator
• struct da9062_regulators
• function da9062_map_buck_mode
• function da9062_buck_set_mode
• function da9062_buck_get_mode
• function da9062_ldo_set_mode
• function da9062_ldo_get_mode
• function da9062_buck_get_status
• function da9062_ldo_get_status
• function da9062_set_suspend_voltage
• function da9062_suspend_enable
• function da9062_suspend_disable
• function da9062_buck_set_suspend_mode
• function da9062_ldo_set_suspend_mode
• function da9062_ldo_lim_event
• function da9062_regulator_probe
• function da9062_regulator_init
• function da9062_regulator_cleanup
• module init da9062_regulator_init

Annotated Snippet

subsys_initcall(da9062_regulator_init);

static void __exit da9062_regulator_cleanup(void)
{
	platform_driver_unregister(&da9062_regulator_driver);
}
module_exit(da9062_regulator_cleanup);

/* Module information */
MODULE_AUTHOR("S Twiss <stwiss.opensource@diasemi.com>");
MODULE_DESCRIPTION("REGULATOR device driver for Dialog DA9062 and DA9061");
MODULE_LICENSE("GPL");
MODULE_ALIAS("platform:da9062-regulators");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/init.h`, `linux/err.h`, `linux/slab.h`, `linux/of.h`, `linux/platform_device.h`, `linux/regmap.h`.
• Detected declarations: `struct da9062_regulator_info`, `struct da9062_regulator`, `struct da9062_regulators`, `function da9062_map_buck_mode`, `function da9062_buck_set_mode`, `function da9062_buck_get_mode`, `function da9062_ldo_set_mode`, `function da9062_ldo_get_mode`, `function da9062_buck_get_status`, `function da9062_ldo_get_status`.
• Atlas domain: Driver Families / drivers/regulator.
• 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.