Skip to main content

Uplift Power Play

Project description


UPP: Uplift Power Play

A tool for parsing, dumping and modifying data in Radeon PowerPlay tables


UPP is able to parse and modify binary data structures of PowerPlay tables commonly found on certain AMD Radeon GPUs. Drivers on recent AMD GPUs allow PowerPlay tables to be dynamically modified on runtime, which may be known as "soft" PowerPlay table. On Linux, the PowerPlay table is by default found at: /sys/class/drm/card0/device/pp_table.

Alternatively, one can use this tool to get PowerPlay data by:

  • Extracting PowerPlay table from Video ROM image (see extract command)
  • Importing "Soft PowerPlay" table from Windows registry, directly from offline Windows/System32/config/SYSTEM file on disk, so it would work from Linux distro that has acces to mounted Windows partition (path to SYSTEM registry file is specified with --from-registry option)

This tool currently supports parsing and modifying PowerPlay tables found on the following AMD GPU families:

  • Polaris
  • Vega
  • Radeon VII
  • Navi 10
  • Navi 14
  • Navi 21 (Sienna Cichlid)

Note: iGPUs found in many recent AMD APUs are using completely different PowerPlay control methods, this tool does not support them.

If you have bugs to report or features to request please create an issue on:


Python 3.6+, click library. Optionally, for reading "soft" PowerPlay table from Windows registry: python-registry. Should work on Windows as well (testers wanted).


At its current form this is a CLI only tool. Getting help:

upp --help


upp <command> --help

Upp will only work by specifying a command which tells it what to do to one's Radeon PowerPlay table data. Currently available commands are:

  • dump - Dumps all PowerPlay data to console
  • extract - Extracts PowerPlay data from full VBIOS ROM image
  • get - Retrieves current value of one or multiple PowerPlay parametter(s)
  • set - Sets value to one or multiple PowerPlay parameters
  • version - Shows UPP version

So, an usage pattern would be like this:


Some generic options applicable to all commands may be used, but please note that they have to be specified before an actual command:

-p, --pp-file <filename>        Input/output PP table file.
-f, --from-registry <filename>  Import PP_PhmSoftPowerPlayTable from Windows
-d, --debug / --no-debug        Debug mode.
-h, --help                      Show help.

Dumping all data:

The dump command de-serializes PowerPlay binary data into a human-readable text output. For example:

upp dump

In standard mode all data will be dumped to console, where data tree hierarchy is indicated by indentation. In raw mode a table showing all hex and binary data, as well as variable names and values, will be dumped.

Extracting PowerPlay table from Video ROM image:

Use extract command for this. The source video ROM binary must be specified with -r/--video-rom parameter, and extracted PowerPlay table will be saved into file specified with generic -p/--pp-file option. For example:

upp --pp-file=extracted.pp_table extract -r VIDEO.rom

Default output file name will be an original ROM file name with an additional .pp_table extension.

Getting PowerPlay table parameter value(s):

The get command retrieves current value of one or multiple PowerPlay table parameter value(s). The parameter variable path must be specified in /<param> notation, for example:

upp get smc_pptable/FreqTableGfx/1 smc_pptable/FreqTableGfx/2

The order of the output values will match the order of the parameter variable paths specified.

Setting PowerPlay table parameter value(s):

The set command sets value to one or multiple PowerPlay table parameter(s). The parameter path and value must be specified in /<param>=<value> notation, for example:

upp -p /tmp/custom-pp_table set --write  \
  smc_pptable/SocketPowerLimitAc/0=100   \
  smc_pptable/SocketPowerLimitDc/0=100   \
  smc_pptable/FanStartTemp=100           \

Note the --write parameter, which has to be specified to actually commit changes to the PowerPlay table file.

Getting upp version

upp version

Running as sudo

Note that if you need to run upp deployed with pip in --user mode with sudo, you'll need to add some parameters to sudo command to make user env available to super-user. For example:

sudo -E env "PATH=$PATH" upp --help

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

upp-0.0.8.tar.gz (60.0 kB view hashes)

Uploaded source

Built Distribution

upp-0.0.8-py3-none-any.whl (77.6 kB view hashes)

Uploaded py3

Supported by

AWS AWS Cloud computing Datadog Datadog Monitoring Facebook / Instagram Facebook / Instagram PSF Sponsor Fastly Fastly CDN Google Google Object Storage and Download Analytics Huawei Huawei PSF Sponsor Microsoft Microsoft PSF Sponsor NVIDIA NVIDIA PSF Sponsor Pingdom Pingdom Monitoring Salesforce Salesforce PSF Sponsor Sentry Sentry Error logging StatusPage StatusPage Status page