drivers/cpuidle/cpuidle-big_little.c
Source file repositories/reference/linux-study-clean/drivers/cpuidle/cpuidle-big_little.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/cpuidle/cpuidle-big_little.c- Extension
.c- Size
- 6663 bytes
- Lines
- 225
- 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.
- 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/cpuidle.hlinux/cpu_pm.hlinux/slab.hlinux/of.hasm/cpu.hasm/cputype.hasm/cpuidle.hasm/mcpm.hasm/smp_plat.hasm/suspend.hdt_idle_states.h
Detected Declarations
function bl_powerdown_finisherfunction bl_enter_powerdownfunction bl_idle_driver_initfunction bl_idle_initmodule init bl_idle_init
Annotated Snippet
device_initcall(bl_idle_init);Annotation
- Immediate include surface: `linux/cpuidle.h`, `linux/cpu_pm.h`, `linux/slab.h`, `linux/of.h`, `asm/cpu.h`, `asm/cputype.h`, `asm/cpuidle.h`, `asm/mcpm.h`.
- Detected declarations: `function bl_powerdown_finisher`, `function bl_enter_powerdown`, `function bl_idle_driver_init`, `function bl_idle_init`, `module init bl_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.