diff options
| author | Mario Limonciello <[email protected]> | 2024-06-26 15:47:22 -0500 |
|---|---|---|
| committer | Rafael J. Wysocki <[email protected]> | 2024-07-01 18:10:52 +0200 |
| commit | 102fa9c4b439ca3bd93d13fb53f5b7592d96a109 (patch) | |
| tree | 8590c28e5b223314f7256e7e461c3547ffe67db4 /scripts/rustdoc_test_builder.rs | |
| parent | 22a40d14b572deb80c0648557f4bd502d7e83826 (diff) | |
cpufreq: Allow drivers to advertise boost enabled
The behavior introduced in commit f37a4d6b4a2c ("cpufreq: Fix per-policy
boost behavior on SoCs using cpufreq_boost_set_sw()") sets up the boost
policy incorrectly when boost has been enabled by the platform firmware
initially even if a driver sets the policy up.
This is because policy_has_boost_freq() assumes that there is a frequency
table set up by the driver and that the boost frequencies are advertised
in that table. This assumption doesn't work for acpi-cpufreq or
amd-pstate. Only use this check to enable boost if it's not already
enabled instead of also disabling it if alreayd enabled.
Fixes: f37a4d6b4a2c ("cpufreq: Fix per-policy boost behavior on SoCs using cpufreq_boost_set_sw()")
Link: https://patch.msgid.link/[email protected]
Reviewed-by: Sibi Sankar <[email protected]>
Reviewed-by: Dhruva Gole <[email protected]>
Acked-by: Viresh Kumar <[email protected]>
Reviewed-by: Gautham R. Shenoy <[email protected]>
Suggested-by: Viresh Kumar <[email protected]>
Suggested-by: Gautham R. Shenoy <[email protected]>
Signed-off-by: Mario Limonciello <[email protected]>
Cc: All applicable <[email protected]>
Signed-off-by: Rafael J. Wysocki <[email protected]>
Diffstat (limited to 'scripts/rustdoc_test_builder.rs')
0 files changed, 0 insertions, 0 deletions