When amd_pstate is running, writing to scaling_min_freq and scaling_max_freq has no effect. These values are only passed to the policy level, but not to the platform level. This means that the platform does not know about the frequency limits set by the user. To fix this, update the min_perf and max_perf values at the platform level whenever the user changes the scaling_min_freq and scaling_max_freq values.
Showing the changes to include/linux (1 of 2 files). Show all
Unified · Split
| @@ -70,6 +70,10 @@ struct amd_cpudata { · 69 unmodified lines | |||
| 70 | u32 nominal_perf; | 70 | u32 nominal_perf; |
| 71 | u32 lowest_nonlinear_perf; | 71 | u32 lowest_nonlinear_perf; |
| 72 | u32 lowest_perf; | 72 | u32 lowest_perf; |
| 73 | u32 min_limit_perf; | ||
| 74 | u32 max_limit_perf; | ||
| 75 | u32 min_limit_freq; | ||
| 76 | u32 max_limit_freq; | ||
| 73 | 77 | ||
| 74 | u32 max_freq; | 78 | u32 max_freq; |
| 75 | u32 min_freq; | 79 | u32 min_freq; |