drivers/cpufreq/cpufreq-dt-platdev.c

File Facts

System

Linux kernel

Corpus path

drivers/cpufreq/cpufreq-dt-platdev.c

Extension

.c

Size

7380 bytes

Lines

247

Domain

Driver Families

Bucket

drivers/cpufreq

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/err.h
• linux/module.h
• linux/of.h
• linux/platform_device.h
• cpufreq-dt.h

Detected Declarations

• function Copyright
• function cpu0_node_has_opp_v2_prop
• function cpufreq_dt_platdev_init
• module init cpufreq_dt_platdev_init

Annotated Snippet

core_initcall(cpufreq_dt_platdev_init);

Annotation

• Immediate include surface: `linux/err.h`, `linux/module.h`, `linux/of.h`, `linux/platform_device.h`, `cpufreq-dt.h`.
• Detected declarations: `function Copyright`, `function cpu0_node_has_opp_v2_prop`, `function cpufreq_dt_platdev_init`, `module init cpufreq_dt_platdev_init`.
• Atlas domain: Driver Families / drivers/cpufreq.
• 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.