drivers/cpufreq/longrun.c
Source file repositories/reference/linux-study-clean/drivers/cpufreq/longrun.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/cpufreq/longrun.c- Extension
.c- Size
- 8277 bytes
- Lines
- 319
- 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.hlinux/module.hlinux/init.hlinux/cpufreq.hlinux/timex.hasm/msr.hasm/processor.hasm/cpu_device_id.hasm/cpuid/api.h
Detected Declarations
function longrun_get_policyfunction longrun_set_policyfunction longrun_verify_policyfunction longrun_getfunction longrun_determine_freqsfunction longrun_cpu_initfunction longrun_initfunction longrun_exitmodule init longrun_init
Annotated Snippet
module_init(longrun_init);
module_exit(longrun_exit);Annotation
- Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/init.h`, `linux/cpufreq.h`, `linux/timex.h`, `asm/msr.h`, `asm/processor.h`, `asm/cpu_device_id.h`.
- Detected declarations: `function longrun_get_policy`, `function longrun_set_policy`, `function longrun_verify_policy`, `function longrun_get`, `function longrun_determine_freqs`, `function longrun_cpu_init`, `function longrun_init`, `function longrun_exit`, `module init longrun_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.