drivers/mfd/ab8500-core.c

File Facts

System

Linux kernel

Corpus path

drivers/mfd/ab8500-core.c

Extension

.c

Size

31649 bytes

Lines

1274

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/slab.h
• linux/init.h
• linux/irq.h
• linux/irqdomain.h
• linux/delay.h
• linux/interrupt.h
• linux/moduleparam.h
• linux/platform_device.h
• linux/mfd/core.h
• linux/mfd/abx500.h
• linux/mfd/abx500/ab8500.h
• linux/mfd/dbx500-prcmu.h
• linux/of.h

Detected Declarations

• function ab8500_prcmu_write
• function ab8500_prcmu_write_masked
• function ab8500_prcmu_read
• function ab8500_get_chip_id
• function set_register_interruptible
• function ab8500_set_register
• function get_register_interruptible
• function ab8500_get_register
• function mask_and_set_register_interruptible
• function ab8500_mask_and_set_register
• function ab8500_irq_lock
• function ab8500_irq_sync_unlock
• function ab8500_irq_mask
• function ab8500_irq_unmask
• function ab8500_irq_set_type
• function update_latch_offset
• function ab8500_handle_hierarchical_line
• function ab8500_handle_hierarchical_latch
• function ab8500_hierarchical_irq
• function ab8500_irq_map
• function ab8500_irq_init
• function ab8500_suspend
• function chip_id_show
• function to
• function ab8500_override_turn_on_stat
• function to
• function turn_on_status_2_show
• function dbbrstn_show
• function dbbrstn_store
• function ab8500_probe
• function ab8500_core_init
• module init ab8500_core_init

Annotated Snippet

core_initcall(ab8500_core_init);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/slab.h`, `linux/init.h`, `linux/irq.h`, `linux/irqdomain.h`, `linux/delay.h`, `linux/interrupt.h`, `linux/moduleparam.h`.
• Detected declarations: `function ab8500_prcmu_write`, `function ab8500_prcmu_write_masked`, `function ab8500_prcmu_read`, `function ab8500_get_chip_id`, `function set_register_interruptible`, `function ab8500_set_register`, `function get_register_interruptible`, `function ab8500_get_register`, `function mask_and_set_register_interruptible`, `function ab8500_mask_and_set_register`.
• 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.