drivers/soc/qcom/rpmh-rsc.c

File Facts

System

Linux kernel

Corpus path

drivers/soc/qcom/rpmh-rsc.c

Extension

.c

Size

35361 bytes

Lines

1157

Domain

Driver Families

Bucket

drivers/soc

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/atomic.h
• linux/cpu_pm.h
• linux/delay.h
• linux/interrupt.h
• linux/io.h
• linux/iopoll.h
• linux/kernel.h
• linux/ktime.h
• linux/list.h
• linux/module.h
• linux/notifier.h
• linux/of.h
• linux/of_irq.h
• linux/of_platform.h
• linux/platform_device.h
• linux/pm_domain.h
• linux/pm_runtime.h
• linux/slab.h
• linux/spinlock.h
• linux/wait.h
• clocksource/arm_arch_timer.h
• soc/qcom/cmd-db.h
• soc/qcom/tcs.h
• dt-bindings/soc/qcom,rpmh-rsc.h
• rpmh-internal.h
• trace-rpmh.h

Detected Declarations

• struct tcs_type_config
• function xloops_to_cycles
• function tcs_reg_addr
• function tcs_cmd_addr
• function read_tcs_cmd
• function read_tcs_reg
• function write_tcs_cmd
• function write_tcs_reg
• function write_tcs_reg_sync
• function tcs_invalidate
• function rpmh_rsc_invalidate
• function get_tcs_for_msg
• function get_req_from_tcs
• function __tcs_set_trigger
• function enable_tcs_irq
• function tcs_tx_done
• function for_each_set_bit
• function program
• function check_for_req_inflight
• function for_each_set_bit_from
• function for_each_set_bit
• function find_free_tcs
• function claim_tcs_for_req
• function rpmh_rsc_send_data
• function find_slots
• function rpmh_rsc_write_ctrl_data
• function rpmh_rsc_ctrlr_is_busy
• function rpmh_rsc_write_next_wakeup
• function rpmh_rsc_cpu_pm_callback
• function rpmh_rsc_pd_callback
• function rpmh_rsc_pd_attach
• function rpmh_probe_tcs_config
• function rpmh_rsc_probe
• function rpmh_driver_init
• module init rpmh_driver_init

Annotated Snippet

core_initcall(rpmh_driver_init);

MODULE_DESCRIPTION("Qualcomm Technologies, Inc. RPMh Driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/atomic.h`, `linux/cpu_pm.h`, `linux/delay.h`, `linux/interrupt.h`, `linux/io.h`, `linux/iopoll.h`, `linux/kernel.h`, `linux/ktime.h`.
• Detected declarations: `struct tcs_type_config`, `function xloops_to_cycles`, `function tcs_reg_addr`, `function tcs_cmd_addr`, `function read_tcs_cmd`, `function read_tcs_reg`, `function write_tcs_cmd`, `function write_tcs_reg`, `function write_tcs_reg_sync`, `function tcs_invalidate`.
• Atlas domain: Driver Families / drivers/soc.
• 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.