Intel PMC Core power management controller for client PCH and SoC platforms
The Power Management Controller block built into Intel's client PCH and SoC silicon, which coordinates package C-states, low-power S0ix sleep, and exposes residency telemetry on modern Core and Core Ultra laptops and desktops. It covers a long line of generations from Skylake-era PCHs up through current parts like Lunar Lake, Arrow Lake, and Panther Lake.
recommendation
It should stay in the kernel because Intel actively extends it with every new client CPU generation. Commits through late 2025 and early 2026 add support for Bartlett Lake, Wildcat Lake, Panther Lake, Lunar Lake, and Arrow Lake, which are all current or upcoming Core Ultra products that ship in laptops and desktops sold new today. The driver provides the telemetry and low-power state plumbing those platforms rely on for suspend, idle residency, and battery life.
repository signals
sources
- cateee.net
LKDDb shows CONFIG_INTEL_PMC_CORE is the in-tree driver for this directory and lists support continuing through current kernels, including newer shared-SSRAM IDs for Arrow Lake, Lunar Lake, and Panther Lake class platforms.
- intel.com
Intel documents Lunar Lake (Intel Core Ultra Series 2) as a current product family, indicating hardware covered by recent intel/pmc enablement was still sold new in 2025.
- intel.com
Intel markets Core Ultra Desktop Processors Series 2 (Arrow Lake generation) as current desktop parts, supporting ongoing new-system deployment for platforms touched by this driver.
codex reasoning notes (technical)
Real driver directory with active entry points and Kconfig. Local `exec_command` on git history showed sustained non-mechanical work through 2025-08-28, 2025-09-11, 2025-10-15, 2025-11-07, and 2026-01-13, including Bartlett Lake, Wildcat Lake, Panther Lake, Lunar Lake, and Arrow Lake support/telemetry updates; a local git grep/log check found no removal or deprecation pattern. URLs were obtained via `web.search_query` (LKDDb and Intel product/support pages). `lei` was unavailable, so upstream-attention evidence came from local git history rather than lore URLs.