drivers/regulator/max8973-regulator.c
Source file repositories/reference/linux-study-clean/drivers/regulator/max8973-regulator.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/regulator/max8973-regulator.c- Extension
.c- Size
- 22258 bytes
- Lines
- 814
- 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.hlinux/module.hlinux/init.hlinux/err.hlinux/of.hlinux/of_device.hlinux/platform_device.hlinux/regulator/driver.hlinux/regulator/machine.hlinux/regulator/max8973-regulator.hlinux/regulator/of_regulator.hlinux/gpio/consumer.hlinux/i2c.hlinux/slab.hlinux/regmap.hlinux/thermal.hlinux/irq.hlinux/interrupt.h
Detected Declarations
struct max8973_chipenum device_idfunction gpiosfunction max8973_dcdc_get_voltage_selfunction max8973_dcdc_set_voltage_selfunction max8973_dcdc_set_modefunction max8973_dcdc_get_modefunction max8973_set_current_limitfunction max8973_get_current_limitfunction max8973_init_dcdcfunction max8973_thermal_read_tempfunction max8973_thermal_irqfunction max8973_thermal_initfunction max8973_probefunction max8973_initfunction max8973_cleanupmodule init max8973_init
Annotated Snippet
subsys_initcall(max8973_init);
static void __exit max8973_cleanup(void)
{
i2c_del_driver(&max8973_i2c_driver);
}
module_exit(max8973_cleanup);
MODULE_AUTHOR("Laxman Dewangan <ldewangan@nvidia.com>");
MODULE_DESCRIPTION("MAX8973 voltage regulator driver");
MODULE_LICENSE("GPL v2");Annotation
- Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/init.h`, `linux/err.h`, `linux/of.h`, `linux/of_device.h`, `linux/platform_device.h`, `linux/regulator/driver.h`.
- Detected declarations: `struct max8973_chip`, `enum device_id`, `function gpios`, `function max8973_dcdc_get_voltage_sel`, `function max8973_dcdc_set_voltage_sel`, `function max8973_dcdc_set_mode`, `function max8973_dcdc_get_mode`, `function max8973_set_current_limit`, `function max8973_get_current_limit`, `function max8973_init_dcdc`.
- 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.