drivers/cpuidle/Kconfig.mips

Source file repositories/reference/linux-study-clean/drivers/cpuidle/Kconfig.mips

File Facts

System: Linux kernel
Corpus path: drivers/cpuidle/Kconfig.mips
Extension: .mips
Size: 646 bytes
Lines: 19
Domain: Driver Families
Bucket: drivers/cpuidle
Inferred role: Driver Families: drivers/cpuidle
Status: atlas-only

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.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0-only
#
# MIPS CPU Idle Drivers
#
config MIPS_CPS_CPUIDLE
	bool "CPU Idle driver for MIPS CPS platforms"
	depends on MIPS_CPS
	depends on SYS_SUPPORTS_MIPS_CPS
	select ARCH_NEEDS_CPU_IDLE_COUPLED if MIPS_MT || CPU_MIPSR6
	select GENERIC_CLOCKEVENTS_BROADCAST if SMP
	select MIPS_CPS_PM
	default y
	help
	  Select this option to enable processor idle state management
	  through cpuidle for systems built around the MIPS Coherent
	  Processing System (CPS) architecture. In order to make use of
	  the deepest idle states you will need to ensure that you are
	  also using the CONFIG_MIPS_CPS SMP implementation.

Annotation

Atlas domain: Driver Families / drivers/cpuidle.
Implementation status: atlas-only.

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.