drivers/cpuidle/cpuidle-arm.c
Source file repositories/reference/linux-study-clean/drivers/cpuidle/cpuidle-arm.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/cpuidle/cpuidle-arm.c- Extension
.c- Size
- 4111 bytes
- Lines
- 169
- 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_cooling.hlinux/cpuidle.hlinux/cpumask.hlinux/cpu_pm.hlinux/kernel.hlinux/module.hlinux/of.hlinux/slab.hasm/cpuidle.hdt_idle_states.h
Detected Declarations
function Copyrightfunction arm_idle_init_cpufunction arm_idle_initfunction for_each_present_cpumodule init arm_idle_init
Annotated Snippet
device_initcall(arm_idle_init);Annotation
- Immediate include surface: `linux/cpu_cooling.h`, `linux/cpuidle.h`, `linux/cpumask.h`, `linux/cpu_pm.h`, `linux/kernel.h`, `linux/module.h`, `linux/of.h`, `linux/slab.h`.
- Detected declarations: `function Copyright`, `function arm_idle_init_cpu`, `function arm_idle_init`, `function for_each_present_cpu`, `module init arm_idle_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.