drivers/cpufreq/cpufreq-nforce2.c
Source file repositories/reference/linux-study-clean/drivers/cpufreq/cpufreq-nforce2.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/cpufreq/cpufreq-nforce2.c- Extension
.c- Size
- 9111 bytes
- Lines
- 436
- 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/moduleparam.hlinux/init.hlinux/cpufreq.hlinux/pci.hlinux/delay.h
Detected Declarations
function nforce2_calc_fsbfunction nforce2_calc_pllfunction nforce2_write_pllfunction nforce2_fsb_readfunction nforce2_set_fsbfunction nforce2_getfunction nforce2_targetfunction nforce2_verifyfunction nforce2_cpu_initfunction nforce2_detect_chipsetfunction nforce2_initfunction nforce2_exitmodule init nforce2_init
Annotated Snippet
module_init(nforce2_init);
module_exit(nforce2_exit);
Annotation
- Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/moduleparam.h`, `linux/init.h`, `linux/cpufreq.h`, `linux/pci.h`, `linux/delay.h`.
- Detected declarations: `function nforce2_calc_fsb`, `function nforce2_calc_pll`, `function nforce2_write_pll`, `function nforce2_fsb_read`, `function nforce2_set_fsb`, `function nforce2_get`, `function nforce2_target`, `function nforce2_verify`, `function nforce2_cpu_init`, `function nforce2_detect_chipset`.
- 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.