drivers/regulator/tps68470-regulator.c

File Facts

System

Linux kernel

Corpus path

drivers/regulator/tps68470-regulator.c

Extension

.c

Size

6644 bytes

Lines

203

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.
• 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/clk.h
• linux/device.h
• linux/err.h
• linux/init.h
• linux/kernel.h
• linux/mfd/tps68470.h
• linux/module.h
• linux/platform_data/tps68470.h
• linux/platform_device.h
• linux/regulator/driver.h
• linux/regulator/machine.h

Detected Declarations

• struct tps68470_regulator_data
• function tps68470_regulator_enable
• function tps68470_regulator_disable
• function tps68470_regulator_probe
• function subsys_initcall
• function tps68470_regulator_exit
• module init tps68470_regulator_init

Annotated Snippet

* subsys_initcall() ensures this when the drivers are builtin.
 */
static int __init tps68470_regulator_init(void)
{
	return platform_driver_register(&tps68470_regulator_driver);
}
subsys_initcall(tps68470_regulator_init);

static void __exit tps68470_regulator_exit(void)
{
	platform_driver_unregister(&tps68470_regulator_driver);
}
module_exit(tps68470_regulator_exit);

MODULE_ALIAS("platform:tps68470-regulator");
MODULE_DESCRIPTION("TPS68470 voltage regulator driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/clk.h`, `linux/device.h`, `linux/err.h`, `linux/init.h`, `linux/kernel.h`, `linux/mfd/tps68470.h`, `linux/module.h`, `linux/platform_data/tps68470.h`.
• Detected declarations: `struct tps68470_regulator_data`, `function tps68470_regulator_enable`, `function tps68470_regulator_disable`, `function tps68470_regulator_probe`, `function subsys_initcall`, `function tps68470_regulator_exit`, `module init tps68470_regulator_init`.
• Atlas domain: Driver Families / drivers/regulator.
• Implementation status: integration 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.