drivers/mfd/da903x.c

File Facts

System

Linux kernel

Corpus path

drivers/mfd/da903x.c

Extension

.c

Size

13202 bytes

Lines

566

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/kernel.h
• linux/module.h
• linux/interrupt.h
• linux/platform_device.h
• linux/i2c.h
• linux/mfd/da903x.h
• linux/slab.h

Detected Declarations

• struct da903x_chip
• struct da903x_chip_ops
• struct da903x_chip
• function __da903x_read
• function __da903x_reads
• function __da903x_write
• function __da903x_writes
• function da903x_register_notifier
• function da903x_unregister_notifier
• function da903x_write
• function da903x_writes
• function da903x_read
• function da903x_reads
• function da903x_set_bits
• function da903x_clr_bits
• function da903x_update
• function da903x_query_status
• function da9030_init_chip
• function da9030_unmask_events
• function da9030_mask_events
• function da9030_read_events
• function da9030_read_status
• function da9034_init_chip
• function da9034_unmask_events
• function da9034_mask_events
• function da9034_read_events
• function da9034_read_status
• function da903x_irq_work
• function da903x_irq_handler
• function __remove_subdev
• function da903x_remove_subdevs
• function da903x_add_subdevs
• function da903x_probe
• function da903x_remove
• function da903x_init
• function da903x_exit
• module init da903x_init
• export da903x_register_notifier
• export da903x_unregister_notifier
• export da903x_write
• export da903x_writes
• export da903x_read
• export da903x_reads
• export da903x_set_bits
• export da903x_clr_bits
• export da903x_update
• export da903x_query_status

Annotated Snippet

subsys_initcall(da903x_init);

static void __exit da903x_exit(void)
{
	i2c_del_driver(&da903x_driver);
}
module_exit(da903x_exit);

MODULE_DESCRIPTION("PMIC Driver for Dialog Semiconductor DA9034");
MODULE_AUTHOR("Eric Miao <eric.miao@marvell.com>");
MODULE_AUTHOR("Mike Rapoport <mike@compulab.co.il>");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/interrupt.h`, `linux/platform_device.h`, `linux/i2c.h`, `linux/mfd/da903x.h`, `linux/slab.h`.
• Detected declarations: `struct da903x_chip`, `struct da903x_chip_ops`, `struct da903x_chip`, `function __da903x_read`, `function __da903x_reads`, `function __da903x_write`, `function __da903x_writes`, `function da903x_register_notifier`, `function da903x_unregister_notifier`, `function da903x_write`.
• 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.