UPDATE 2024-02-28: power-profiles-daemon v0.20 was released on 2024-02-15. That version added support for multiple drivers, such that both platform_profile and amd_pstate may be controlled simultaneously. That version is already deployed for Fedora 39, and other distros will eventually follow. If you use PPD v0.20++, you should NOT use this pstate_update daemon, as they might easily conflict each other.

power-profiles-daemon is a nice and simple daemon which controls the power states in both Gnome and KDE. It supports several Linux power "drivers", like platform_profile, amd_pstate, intel_pstate, etc. However, it can currently use only one of these drivers, not multiple of them at the same time.

Some computers like ThinkPad T14 G3 AMD, exposes multiple of the available interfaces (eg. both platform_profiles and amd_pstate). power-profiles-daemon will then only control the platform_profile, while amd_pstate remains uncontrolled. It turns out that amd_pstate Energy Performance Preference (EPP) remains at performance in my case, which burns a lot of excess energy when I do not need it. To fix this, I wrote this small daemon which does the following:

• Use the DBus interface for power-profiles-daemon and listen for ActiveProfile property changes.
• Translate the PPD power profile to a desired AMD PState EPP.
• Write the selected AMD PState EPP to the kernel sysfs interface. This is written on all available CPU cores/threads that are exposed.

It also comes with a conveniet systemd unit file to launch the service in the background.

There are pre-built binaries available for download in the Releases section. Otherwise, the project is built using cargo. Nothing special there.

cargo build --release

Configure the mapping from Power Profile to EPP and scaling governor in a config.toml file. The file should preferrably be placed in /etc/pstate_update/config.toml, but a local config.toml file is also accepted. This repo contains a sample config.toml with a reasonable configuration for low power consumption.

For convenience, there is also a small deployment script which copies files to various places (deploy.sh). If you use the deployment script, you should only need the following two commands.

./deploy.sh
sudo systemctl start pstate_update.service

Make sure to also enable the systemd service if you want it to start automatically.

sudo systemctl enable pstate_update.service