drivers/cpuidle/cpuidle-cps.c
Source file repositories/reference/linux-study-clean/drivers/cpuidle/cpuidle-cps.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/cpuidle/cpuidle-cps.c- Extension
.c- Size
- 4283 bytes
- Lines
- 179
- Domain
- Driver Families
- Bucket
- drivers/cpuidle
- 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/cpu_pm.hlinux/cpuidle.hlinux/init.hasm/idle.hasm/pm-cps.h
Detected Declarations
enum cps_idle_statefunction cps_nc_enterfunction cps_cpuidle_unregisterfunction for_each_possible_cpufunction cps_cpuidle_initfunction for_each_possible_cpumodule init cps_cpuidle_init
Annotated Snippet
device_initcall(cps_cpuidle_init);Annotation
- Immediate include surface: `linux/cpu_pm.h`, `linux/cpuidle.h`, `linux/init.h`, `asm/idle.h`, `asm/pm-cps.h`.
- Detected declarations: `enum cps_idle_state`, `function cps_nc_enter`, `function cps_cpuidle_unregister`, `function for_each_possible_cpu`, `function cps_cpuidle_init`, `function for_each_possible_cpu`, `module init cps_cpuidle_init`.
- Atlas domain: Driver Families / drivers/cpuidle.
- 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.