Detailed explanation of configuration decisions and hardware-specific optimizations.
Architecture:
- 12 total cores:
- 2 P-cores (Performance): 1.3 GHz base → 4.3 GHz turbo (with Hyper-Threading)
- 8 E-cores (Efficient): 800 MHz base → 3.6 GHz turbo
- 2 LP E-cores (Low Power Efficient): 700 MHz base → 2.1 GHz turbo
- 14 total threads (only P-cores have HT)
- 12 MB L3 Cache
Power Consumption:
- Processor Base Power: 15W (OEM configured nominal TDP)
- Maximum Turbo Power: 57W (PL2 - short performance bursts)
- Minimum Assured Power: 12W (guaranteed minimum consumption)
Relevant Features for TLP:
- ✅ Supports intel_pstate driver in active mode (HWP - Hardware P-States)
- ✅ Supports EPP (Energy Performance Preference) - HWP.EPP
- ✅ Supports Turbo Boost 2.0
- ✅ Supports HWP Dynamic Boost
- ✅ Does NOT support EPB (because it has EPP, they're mutually exclusive)
Integrated GPU:
- Intel Arc Graphics (4-cores)
- Frequencies: 800 MHz min → 1850 MHz max
- Based on Xe-LPG architecture
What it is: Energy Performance Preference for CPUs with HWP support.
Available values (in order of increasing power saving):
performance- Maximum performance, high consumptionbalance_performance- Good performance with moderate consumptiondefault- Kernel default (translates to balance_performance)balance_power- Balance favoring power savingpower- Maximum power saving
Our configuration:
- AC:
balance_performance(good performance without excessive heat) - BAT:
power(aggressive power saving) - SAV:
power(maximum power saving)
Why this matters: EPP is THE most important parameter for modern Intel CPUs. Has more impact than frequency scaling or governors.
What it is: Performance limit as percentage of total available.
How it works: Limits maximum P-state CPU can reach. At 80%, CPU won't use more than 80% of its maximum capacity, which in practice means lower maximum frequencies.
Our configuration:
- AC:
100%(no limits) - BAT:
80%(limit to ~3.0-3.2 GHz max) - SAV:
50%(limit to ~1.8-2.0 GHz max) - customized from default 40%
Impact: Direct control over maximum CPU performance and consumption.
What it is: Turbo Boost control (Intel) / Core Performance Boost (AMD).
How it works:
0= disable (CPU limited to base frequencies)1= allow (CPU can exceed base frequency if thermal/power budget available)
Our configuration:
- AC:
1(enabled - allow turbo up to 4.3 GHz) - BAT:
0(disabled - stay at more efficient frequencies) - SAV:
0(disabled)
Why disable on battery: Turbo boost is the #1 battery life enemy. Consumes disproportionately more power for relatively small performance gain.
Impact: Disabling turbo on battery can save 40-50% consumption in CPU-intensive tasks.
What it is: HWP Dynamic Boost improves responsiveness by dynamically raising minimum P-state when a task previously waiting on I/O becomes runnable.
Requirements: Intel Core i 6th gen or newer with intel_pstate in active mode.
Our configuration:
- AC:
1(enabled - better interactive response) - BAT:
0(disabled - avoid unnecessary consumption spikes) - SAV:
0(disabled)
Why it matters: Specific to modern CPUs with HWP. Many configurations miss this parameter.
Impact: ~0.2W savings on battery + better responsiveness on AC.
What it is: System-wide operating profile affecting not just CPU but entire platform (I/O controllers, memory, firmware).
Available options on ThinkPad E14 Gen 6:
performance- Maximum performancebalanced- Balance between performance and consumptionlow-power- Maximum power saving
Our configuration:
- AC:
balanced(good performance without excessive fan noise) - BAT:
low-power(maximum platform-wide savings) - SAV:
low-power
Why not 'performance' on AC: performance makes fans run louder and system hotter without significant real-world benefit for typical tasks.
What it is: Runtime Power Management for AHCI/NVMe controllers.
How it works: Allows disk controller to enter low power states when not actively reading/writing.
Our configuration:
- AC:
on(disabled - better responsiveness, no wake-up latency) - BAT:
auto(enabled - power savings)
Timeout: 15 seconds of inactivity before suspending
Impact: 0.5-1W savings when disk inactive. Important for NVMe SSDs.
What it is: Non-Maskable Interrupt Watchdog for kernel debugging.
Problem: When enabled, constantly interrupts CPU preventing it from entering deep C-states.
Our configuration: 0 (disabled)
Impact: 0.5-1W savings by allowing deeper C-states.
When to enable: Only for kernel debugging. Normal users should keep disabled.
| Mode | Before | After | Savings |
|---|---|---|---|
| AC | ~15W | ~10-13W | 20-30% |
| BAT | ~15W | ~5-7W | 60-65% |
| SAV | ~15W | ~4-6W | 70-75% |
| Mode | Estimated Duration |
|---|---|
| BAT (light use) | 6-8 hours |
| BAT (typical use) | 5-6 hours |
| SAV (light use) | 8-10 hours |
| Mode | Typical Freq | Max Freq | Turbo | Temp (idle) |
|---|---|---|---|---|
| AC | 1.5-2.5 GHz | 4.3 GHz | ON | 50-55°C |
| BAT | 0.8-2.0 GHz | 3.2 GHz | OFF | 40-50°C |
| SAV | 0.8-1.5 GHz | 2.0 GHz | OFF | 40-45°C |
Why 80%:
- Allows good burst performance when needed (3.0-3.2 GHz)
- Prevents reaching most power-hungry frequencies (>3.5 GHz)
- Good balance for daily tasks (browsing, office, programming)
Too low (60%): May feel sluggish for some tasks
Too high (90-100%): Minimal additional savings vs BAT mode purpose
Why 50% (custom):
- Original default was 40%
- User found 40% too restrictive for their needs
- 50% provides slightly better responsiveness while maintaining excellent savings
Flexibility: This is the beauty of the modular configuration - easy to customize.
Not "maximum performance" but "balanced". Why?
- Most tasks don't need constant 4.3 GHz
- Fans stay quieter
- System stays cooler
- Negligible real-world performance difference for typical work
Not "maximum savings" but "practical". Why?
- Still very usable for daily work
- Good battery life (6-8 hours)
- Only activate SAV when truly needed
Manual activation only. Why?
- Noticeably slower - not for regular use
- For specific situations (long flight, low battery, etc.)
- User decides when to make the tradeoff
- HWP Dynamic Boost: Must be configured (many guides miss this)
- EPP over governor: Modern CPUs use EPP, not traditional governors
- Platform Profile: Controls entire SoC, not just CPU
- No EPB: This CPU uses EPP, EPB doesn't apply
- Battery thresholds: Supported via thinkpad_acpi
- No dGPU: Only integrated graphics, no AMD/NVIDIA config needed
- NVMe SSD: Runtime PM matters (not traditional disk APM)
- Single battery: No BAT1 configuration needed
Last updated: 2026-02-16
Hardware: ThinkPad E14 Gen 6 - Intel Core Ultra 5 125U