configs/raspberrypi*: stop setting powersave as the default CPU governor #523
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The defconfigs from the RPi Kernel set
powersave
as the default CPU governor, which is a bad idea as that reduces performance by setting the CPU frequency to the minimum one.In case of a buildroot build user-space is not configured by default to change the CPU governor, so
powersave
will remain the CPU governor and it will slow down everything.This patch unsets the selection of
powersave
as the default CPU governor.Then the CPU governor that will be selected as default after this patch will be the Linux's default one that is either one of:
ondemand
,schedutil
orperformance
depending on the Kernel version and the hardware. For modern Kernels (>v5.6)schedutil
is the one preferred for ARM hardware. See Linux Kernel commit: https://git.kernel.org/linus/f259eab3ea0e7eThis patch was submitted upstream (both to the RPi kernel defconfigs and to upstream buildroot but was not accepted). See: https://lists.buildroot.org/pipermail/buildroot/2023-October/677641.html and configs: stop defaulting to the powersave governor raspberrypi/linux#5666
This PR already updates all RPi defconfigs, but in the future if new defconfigs are added for RPi boards then this command can be used to automate updating them: