One side-effect of fixing the scaling frequency limits using the commit eacc9c5a927e ("cpufreq: intel_pstate: Fix intel_pstate_get_hwp_max() for turbo disabled") causes stale HWP_CAP.GUARANTEED to be used as max. Without processing HWP interrupts, user space needs to be able to update a new max while Intel SST is in use. This is not a problem as the change of guaranteed is caused by user space action, so user space knows that guarantee will change. This series causes user space to trigger scaling_max_freq update with the new base_frequency. Srinivas Pandruvada (2): tools/power/x86/intel-speed-select: Set scaling_max_freq to base_frequency tools/power/x86/intel-speed-select: Set higher of cpuinfo_max_freq or base_frequency .../x86/intel-speed-select/isst-config.c | 32 +++++++++++++++++++ 1 file changed, 32 insertions(+) -- 2.29.2