drivers/cpufreq/s3c64xx-cpufreq.c

File Facts

System

Linux kernel

Corpus path

drivers/cpufreq/s3c64xx-cpufreq.c

Extension

.c

Size

5081 bytes

Lines

212

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/kernel.h
• linux/types.h
• linux/init.h
• linux/cpufreq.h
• linux/clk.h
• linux/err.h
• linux/regulator/consumer.h
• linux/module.h

Detected Declarations

• struct s3c64xx_dvfs
• function s3c64xx_cpufreq_set_target
• function s3c64xx_cpufreq_config_regulator
• function cpufreq_for_each_valid_entry
• function s3c64xx_cpufreq_driver_init
• function cpufreq_for_each_entry
• function s3c64xx_cpufreq_init
• module init s3c64xx_cpufreq_init

Annotated Snippet

module_init(s3c64xx_cpufreq_init);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/types.h`, `linux/init.h`, `linux/cpufreq.h`, `linux/clk.h`, `linux/err.h`, `linux/regulator/consumer.h`, `linux/module.h`.
• Detected declarations: `struct s3c64xx_dvfs`, `function s3c64xx_cpufreq_set_target`, `function s3c64xx_cpufreq_config_regulator`, `function cpufreq_for_each_valid_entry`, `function s3c64xx_cpufreq_driver_init`, `function cpufreq_for_each_entry`, `function s3c64xx_cpufreq_init`, `module init s3c64xx_cpufreq_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.