drivers/cpufreq/cpufreq.c
Source file repositories/reference/linux-study-clean/drivers/cpufreq/cpufreq.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/cpufreq/cpufreq.c- Extension
.c- Size
- 82191 bytes
- Lines
- 3083
- 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.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/cpu.hlinux/cpufreq.hlinux/cpu_cooling.hlinux/delay.hlinux/device.hlinux/init.hlinux/kernel_stat.hlinux/module.hlinux/mutex.hlinux/pm_qos.hlinux/slab.hlinux/string_choices.hlinux/suspend.hlinux/syscore_ops.hlinux/tick.hlinux/units.htrace/events/power.h
Detected Declarations
function cpufreq_supports_freq_invariancefunction has_targetfunction has_target_indexfunction cpufreq_disabledfunction disable_cpufreqfunction have_governor_per_policyfunction get_cpu_idle_timefunction initfunction cpufreq_generic_getfunction cpufreq_cpu_get_rawfunction cpufreq_cpu_putfunction adjust_jiffiesfunction adjust_jiffiesfunction cpufreq_notify_post_transitionfunction cpufreq_freq_transition_beginfunction cpufreq_freq_transition_endfunction cpufreq_list_transition_notifiersfunction cpufreq_enable_fast_switchfunction cpufreq_disable_fast_switchfunction __resolve_freqfunction cpufreq_driver_resolve_freqfunction cpufreq_policy_transition_delay_usfunction show_boostfunction store_boostfunction show_local_boostfunction policy_set_boostfunction store_local_boostfunction cpufreq_parse_policyfunction arch_freq_get_on_cpufunction cpufreq_avg_freq_supportedfunction show_scaling_cur_freqfunction show_cpuinfo_cur_freqfunction show_cpuinfo_avg_freqfunction show_scaling_governorfunction store_scaling_governorfunction show_scaling_driverfunction show_scaling_available_governorsfunction cpufreq_show_cpusfunction for_each_cpufunction show_related_cpusfunction show_affected_cpusfunction store_scaling_setspeedfunction show_scaling_setspeedfunction show_bios_limitfunction showfunction storefunction cpufreq_sysfs_releasefunction add_cpu_dev_symlink
Annotated Snippet
core_initcall(cpufreq_core_init);
Annotation
- Immediate include surface: `linux/cpu.h`, `linux/cpufreq.h`, `linux/cpu_cooling.h`, `linux/delay.h`, `linux/device.h`, `linux/init.h`, `linux/kernel_stat.h`, `linux/module.h`.
- Detected declarations: `function cpufreq_supports_freq_invariance`, `function has_target`, `function has_target_index`, `function cpufreq_disabled`, `function disable_cpufreq`, `function have_governor_per_policy`, `function get_cpu_idle_time`, `function init`, `function cpufreq_generic_get`, `function cpufreq_cpu_get_raw`.
- Atlas domain: Driver Families / drivers/cpufreq.
- Implementation status: integration implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
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.