[Bug 205979] New: [amdgpu] Vega10 forcing power_dpm_force_performance_level to "high" or "profile_peak", followed by "auto", "low", or "profile_min_mclk" has memory clock stuck at max state

[Bug 205979] New: [amdgpu] Vega10 forcing power_dpm_force_performance_level to "high" or "profile_peak", followed by "auto", "low", or "profile_min_mclk" has memory clock stuck at max state

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=205979

            Bug ID: 205979
           Summary: [amdgpu] Vega10 forcing
                    power_dpm_force_performance_level to "high" or
                    "profile_peak", followed by "auto", "low", or
                    "profile_min_mclk" has memory clock stuck at max state
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.4.6-gentoo
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: stefanspr94@gmail.com
        Regression: No

Memory can only be brought back to lower clocks when setting
power_dpm_force_performance_level to "manual" and forcing a lower socclk state
eg. "2" in pp_dpm_socclk or by rebooting.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel