Allow for only setting Minimum CPU / GPU Clock(s) with no Maximum #106

Open
opened 2023-05-25 18:11:10 +01:00 by syberphunk · 6 comments
syberphunk commented 2023-05-25 18:11:10 +01:00 (Migrated from github.com)

Please confirm

  • I have searched existing issues
  • This issue is not a duplicate of an existing one
  • I will fill this out to the best of my ability

Describe what you'd like to be able to do

Steam Deck users are overclocking the GPU and CPU using tools such as https://github.com/DavidS95/Smokeless_UMAF

PowerTools allows us to configure an override to accommodate these higher values for GPU and CPU clock, but a current bug with amdgpu prevents us from setting higher than stock clock speeds.

If we set no maximum value, the Steam Deck with these overclocks in place will automatically scale upwards.

Unfortunately we cannot currently set only a 'minimum' without also setting a 'maximum' and take advantage of these overclock values.

Some games, emulators, etc. need minimum clock values to be set because the automatic scaling of its frequency may not be appropriate for the game or software that's being run, even if it won't scale higher than this minimum value.

Therefore it would be good to be able to set a minimum value, without enforcing a maximum value for the clock speeds.

It would be good to be able to set this option of 'no maximum values for clocks' in the user interface, else editing pt_oc.json would be an alternative workaround to permit it.

Describe alternatives you've considered

There's no real other alternative aside from not setting clock minimum/maximum at all per game, and this removes the ability to hold the APU accountable to run at least at a minimum speed.

Anything else?

No response

### Please confirm - [X] I have searched existing issues - [X] This issue is not a duplicate of an existing one - [X] I will fill this out to the best of my ability ### Describe what you'd like to be able to do Steam Deck users are overclocking the GPU and CPU using tools such as https://github.com/DavidS95/Smokeless_UMAF PowerTools allows us to configure an override to accommodate these higher values for GPU and CPU clock, but a current bug with amdgpu prevents us from setting higher than stock clock speeds. If we set no maximum value, the Steam Deck with these overclocks in place will automatically scale upwards. Unfortunately we cannot currently set only a 'minimum' without also setting a 'maximum' and take advantage of these overclock values. Some games, emulators, etc. need minimum clock values to be set because the automatic scaling of its frequency may not be appropriate for the game or software that's being run, even if it won't scale higher than this minimum value. Therefore it would be good to be able to set a minimum value, without enforcing a maximum value for the clock speeds. It would be good to be able to set this option of 'no maximum values for clocks' in the user interface, else editing pt_oc.json would be an alternative workaround to permit it. ### Describe alternatives you've considered There's no real other alternative aside from not setting clock minimum/maximum at all per game, and this removes the ability to hold the APU accountable to run at least at a minimum speed. ### Anything else? _No response_
DenoG1997 commented 2023-05-26 14:43:31 +01:00 (Migrated from github.com)

did you know a workaround for this because when I set a custom freq then it will apply as soon I get the slider under 3500 MHz

did you know a workaround for this because when I set a custom freq then it will apply as soon I get the slider under 3500 MHz
NGnius commented 2023-05-26 20:40:20 +01:00 (Migrated from github.com)

There's always equivalent commands

There's always equivalent commands
syberphunk commented 2023-05-26 20:58:23 +01:00 (Migrated from github.com)

Having the controls via GUI is convenient and the whole purpose of having decky plugins.

Having the controls via GUI is convenient and the whole purpose of having decky plugins.
NGnius commented 2023-05-26 22:02:55 +01:00 (Migrated from github.com)

Agreed, my suggestion was strictly in the context of being a workaround. There is also a Decky plugin for running commands.

Agreed, my suggestion was strictly in the context of being a workaround. There is also a Decky plugin for running commands.
syberphunk commented 2023-05-28 22:05:08 +01:00 (Migrated from github.com)

Noting this as related: https://github.com/badly-drawn-wizards/vangogh_oc_fix as observed by JDGBOLT. Not suggesting this is within scope of PowerTools.

Noting this as related: https://github.com/badly-drawn-wizards/vangogh_oc_fix as observed by JDGBOLT. Not suggesting this is within scope of PowerTools.
badly-drawn-wizards commented 2023-06-18 17:13:03 +01:00 (Migrated from github.com)

Just chipping in to say that I have filed an issue. Although I have little hope that it will be implemented and if it does it will be a long while until it trickles down to SteamOS:
https://gitlab.freedesktop.org/drm/amd/-/issues/2638

I hope my fix becomes irrelevant as fast as possible. 🙏

Just chipping in to say that I have filed an issue. Although I have little hope that it will be implemented and if it does it will be a long while until it trickles down to SteamOS: https://gitlab.freedesktop.org/drm/amd/-/issues/2638 I hope my fix becomes irrelevant as fast as possible. :pray:
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: NG-SD-Plugins/PowerTools#106
No description provided.