drivers/clk/samsung/clk-exynos8895.c

File Facts

System

Linux kernel

Corpus path

drivers/clk/samsung/clk-exynos8895.c

Extension

.c

Size

136732 bytes

Lines

2804

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/mod_devicetable.h
• linux/of.h
• linux/platform_device.h
• dt-bindings/clock/samsung,exynos8895.h
• clk.h
• clk-exynos-arm64.h

Detected Declarations

• function exynos8895_cmu_top_init
• function exynos8895_cmu_peris_init
• function exynos8895_cmu_probe
• function exynos8895_cmu_init
• module init exynos8895_cmu_init

Annotated Snippet

core_initcall(exynos8895_cmu_init);

Annotation

• Immediate include surface: `linux/clk-provider.h`, `linux/mod_devicetable.h`, `linux/of.h`, `linux/platform_device.h`, `dt-bindings/clock/samsung,exynos8895.h`, `clk.h`, `clk-exynos-arm64.h`.
• Detected declarations: `function exynos8895_cmu_top_init`, `function exynos8895_cmu_peris_init`, `function exynos8895_cmu_probe`, `function exynos8895_cmu_init`, `module init exynos8895_cmu_init`.
• 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.