drivers/mfd/db8500-prcmu.c

File Facts

System

Linux kernel

Corpus path

drivers/mfd/db8500-prcmu.c

Extension

.c

Size

80274 bytes

Lines

3093

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/init.h
• linux/export.h
• linux/kernel.h
• linux/delay.h
• linux/errno.h
• linux/err.h
• linux/spinlock.h
• linux/io.h
• linux/slab.h
• linux/mutex.h
• linux/completion.h
• linux/irq.h
• linux/jiffies.h
• linux/bitops.h
• linux/fs.h
• linux/of.h
• linux/of_address.h
• linux/of_irq.h
• linux/platform_device.h
• linux/uaccess.h
• linux/mfd/core.h
• linux/mfd/dbx500-prcmu.h
• linux/mfd/abx500/ab8500.h
• linux/regulator/db8500-prcmu.h
• linux/regulator/machine.h
• db8500-prcmu-regs.h

Detected Declarations

• struct clk_mgt
• struct dsiclk
• struct dsiescclk
• function db8500_prcmu_read
• function db8500_prcmu_write
• function db8500_prcmu_write_masked
• function prcmu_is_ulppll_disabled
• function prcmu_has_arm_maxopp
• function prcmu_set_rc_a2p
• function prcmu_get_rc_p2a
• function prcmu_get_xp70_current_state
• function outputs
• function db8500_prcmu_set_power_state
• function db8500_prcmu_get_power_state_result
• function config_wakeups
• function db8500_prcmu_enable_wakeups
• function db8500_prcmu_config_abb_event_readout
• function db8500_prcmu_get_abb_event_buffer
• function db8500_prcmu_set_arm_opp
• function db8500_prcmu_get_arm_opp
• function db8500_prcmu_get_ddr_opp
• function request_even_slower_clocks
• function db8500_prcmu_set_ape_opp
• function db8500_prcmu_get_ape_opp
• function db8500_prcmu_request_ape_opp_100_voltage
• function prcmu_release_usb_wakeup_state
• function request_pll
• function EPOD
• function msecs_to_jiffies
• function prcmu_configure_auto_pm
• function prcmu_is_auto_pm_enabled
• function request_sysclk
• function msecs_to_jiffies
• function request_timclk
• function request_clock
• function request_sga_clock
• function plldsi_locked
• function request_plldsi
• function request_dsiclk
• function request_dsiescclk
• function db8500_prcmu_request_clock
• function pll_rate
• function clock_rate
• function armss_rate
• function dsiclk_rate
• function dsiescclk_rate
• function prcmu_clock_rate
• function clock_source_rate

Annotated Snippet

core_initcall(db8500_prcmu_init);

Annotation

• Immediate include surface: `linux/init.h`, `linux/export.h`, `linux/kernel.h`, `linux/delay.h`, `linux/errno.h`, `linux/err.h`, `linux/spinlock.h`, `linux/io.h`.
• Detected declarations: `struct clk_mgt`, `struct dsiclk`, `struct dsiescclk`, `function db8500_prcmu_read`, `function db8500_prcmu_write`, `function db8500_prcmu_write_masked`, `function prcmu_is_ulppll_disabled`, `function prcmu_has_arm_maxopp`, `function prcmu_set_rc_a2p`, `function prcmu_get_rc_p2a`.
• 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.