drivers/clk/rockchip/clk-rk3588.c

File Facts

System

Linux kernel

Corpus path

drivers/clk/rockchip/clk-rk3588.c

Extension

.c

Size

119641 bytes

Lines

2534

Domain

Driver Families

Bucket

drivers/clk

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/clk-provider.h
• linux/of.h
• linux/of_address.h
• linux/platform_device.h
• linux/syscore_ops.h
• dt-bindings/clock/rockchip,rk3588-cru.h
• clk.h

Detected Declarations

• enum rk3588_plls
• function rk3588_clk_early_init
• function clk_rk3588_probe
• function rockchip_clk_rk3588_drv_register
• module init rockchip_clk_rk3588_drv_register

Annotated Snippet

core_initcall(rockchip_clk_rk3588_drv_register);

Annotation

• Immediate include surface: `linux/clk-provider.h`, `linux/of.h`, `linux/of_address.h`, `linux/platform_device.h`, `linux/syscore_ops.h`, `dt-bindings/clock/rockchip,rk3588-cru.h`, `clk.h`.
• Detected declarations: `enum rk3588_plls`, `function rk3588_clk_early_init`, `function clk_rk3588_probe`, `function rockchip_clk_rk3588_drv_register`, `module init rockchip_clk_rk3588_drv_register`.
• Atlas domain: Driver Families / drivers/clk.
• 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.