Bug 110208 - New GPU sysfs Power State Interface for custom pp_od_clk_voltage
Summary: New GPU sysfs Power State Interface for custom pp_od_clk_voltage
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-20 11:48 UTC by famo
Modified: 2019-11-19 09:17 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description famo 2019-03-20 11:48:27 UTC
In order to use a custom pp_od_clk_voltage one has to set power_dpm_force_performance_level to manual.

However this way it is not possible to use custom pp_od_clk_voltage and force - for instance - high or peak performance levels.


The forcing of different performance levels doesn't (and shouldn't) relate to custom clocks/voltages. Putting this setting in the same interface is a poor choice and (unnecessarily) restricts the possibilities.


Please add a new sysfs interface for *solely* choosing between default and custom pp_od_clk_voltage.
Comment 1 famo 2019-03-20 11:50:50 UTC
Link to  documentation:
https://dri.freedesktop.org/docs/drm/gpu/amdgpu.html#power-dpm-force-performance-level

Quote:
pp_od_clk_voltage

The amdgpu driver provides a sysfs API for adjusting the clocks and voltages in each power level within a power state. The pp_od_clk_voltage is used for this.

< For Vega10 and previous ASICs >

Reading the file will display:

    a list of engine clock levels and voltages labeled OD_SCLK
    a list of memory clock levels and voltages labeled OD_MCLK
    a list of valid ranges for sclk, mclk, and voltage labeled OD_RANGE

To manually adjust these settings, first select manual using power_dpm_force_performance_level. ...
Comment 2 Martin Peres 2019-11-19 09:17:55 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/731.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.