drivers/mfd/tps6586x.c
Source file repositories/reference/linux-study-clean/drivers/mfd/tps6586x.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/mfd/tps6586x.c- Extension
.c- Size
- 16959 bytes
- Lines
- 675
- Domain
- Driver Families
- Bucket
- drivers/mfd
- 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.
- 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/interrupt.hlinux/irq.hlinux/irqdomain.hlinux/kernel.hlinux/module.hlinux/mutex.hlinux/slab.hlinux/err.hlinux/i2c.hlinux/platform_device.hlinux/reboot.hlinux/regmap.hlinux/of.hlinux/mfd/core.hlinux/mfd/tps6586x.h
Detected Declarations
struct tps6586x_irq_datastruct tps6586xfunction tps6586x_writefunction tps6586x_writesfunction tps6586x_readfunction tps6586x_readsfunction tps6586x_set_bitsfunction tps6586x_clr_bitsfunction tps6586x_updatefunction tps6586x_irq_get_virqfunction tps6586x_get_versionfunction __remove_subdevfunction tps6586x_remove_subdevsfunction tps6586x_irq_lockfunction tps6586x_irq_enablefunction tps6586x_irq_disablefunction tps6586x_irq_sync_unlockfunction tps6586x_irq_set_wakefunction tps6586x_irq_mapfunction tps6586x_irqfunction tps6586x_irq_initfunction tps6586x_add_subdevsfunction is_volatile_regfunction tps6586x_power_off_handlerfunction tps6586x_restart_handlerfunction tps6586x_print_versionfunction tps6586x_i2c_probefunction tps6586x_i2c_removefunction tps6586x_i2c_suspendfunction tps6586x_i2c_resumefunction tps6586x_initfunction tps6586x_exitmodule init tps6586x_initexport tps6586x_writeexport tps6586x_writesexport tps6586x_readexport tps6586x_readsexport tps6586x_set_bitsexport tps6586x_clr_bitsexport tps6586x_updateexport tps6586x_irq_get_virqexport tps6586x_get_version
Annotated Snippet
subsys_initcall(tps6586x_init);
static void __exit tps6586x_exit(void)
{
i2c_del_driver(&tps6586x_driver);
}
module_exit(tps6586x_exit);
MODULE_DESCRIPTION("TPS6586X core driver");
MODULE_AUTHOR("Mike Rapoport <mike@compulab.co.il>");
Annotation
- Immediate include surface: `linux/interrupt.h`, `linux/irq.h`, `linux/irqdomain.h`, `linux/kernel.h`, `linux/module.h`, `linux/mutex.h`, `linux/slab.h`, `linux/err.h`.
- Detected declarations: `struct tps6586x_irq_data`, `struct tps6586x`, `function tps6586x_write`, `function tps6586x_writes`, `function tps6586x_read`, `function tps6586x_reads`, `function tps6586x_set_bits`, `function tps6586x_clr_bits`, `function tps6586x_update`, `function tps6586x_irq_get_virq`.
- Atlas domain: Driver Families / drivers/mfd.
- Implementation status: integration implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
- 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.