drm/amd/pm: Fix showing incorrect frequencies on aldebaran

Browse source

v1: Use the current and custom pstate frequencies to track the current and
user-set min/max values in manual and determinism mode. Previously, only
actual_* value was used to track the currrent and user requested value.
The value will get reassigned whenever user requests a new value with
pp_od_clk_voltage node. Hence it will show incorrect values when user
requests an invalid value or tries a partial request without committing
the values. Separating out to custom and current variable fixes such
issues.

v2: Remove redundant if-else check

Signed-off-by: Lijo Lazar <lijo.lazar@amd.com>
Reviewed-by: Kevin Wang <kevin1.wang@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

...

This commit is contained in:

Lijo Lazar 2021-05-13 15:51:18 +08:00 • committed by Alex Deucher

parent eed13b0e37

commit e943dd8861

2 changed files with 55 additions and 25 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

75

drivers/gpu/drm/amd/pm/swsmu/smu13/aldebaran_ppt.c

View file

9

drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0.c

View file