drivers/soc/rockchip/dtpm.c

File Facts

System

Linux kernel

Corpus path

drivers/soc/rockchip/dtpm.c

Extension

.c

Size

1782 bytes

Lines

66

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

Dependency Surface

• linux/dtpm.h
• linux/module.h
• linux/of.h
• linux/platform_device.h

Detected Declarations

• function rockchip_dtpm_init
• function rockchip_dtpm_exit
• module init rockchip_dtpm_init

Annotated Snippet

module_init(rockchip_dtpm_init);

static void __exit rockchip_dtpm_exit(void)
{
	return dtpm_destroy_hierarchy();
}
module_exit(rockchip_dtpm_exit);

MODULE_SOFTDEP("pre: panfrost cpufreq-dt");
MODULE_DESCRIPTION("Rockchip DTPM driver");
MODULE_LICENSE("GPL");
MODULE_ALIAS("platform:dtpm");
MODULE_AUTHOR("Daniel Lezcano <daniel.lezcano@kernel.org");

Annotation

• Immediate include surface: `linux/dtpm.h`, `linux/module.h`, `linux/of.h`, `linux/platform_device.h`.
• Detected declarations: `function rockchip_dtpm_init`, `function rockchip_dtpm_exit`, `module init rockchip_dtpm_init`.
• Atlas domain: Driver Families / drivers/soc.
• Implementation status: integration implementation candidate.

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.