rsday, October 13, 2016 6:04 AM
> To: Quan, Evan <evan.q...@amd.com>; amd-gfx@lists.freedesktop.org
> Cc: Zhang, Jerry <jerry.zh...@amd.com>; Huan, Alvin
> <alvin.h...@amd.com>; Quan, Evan <evan.q...@amd.com>; Huang, Ray
> <ray.hu...@amd.com>
> Subject
.deuc...@amd.com>; amd-
> g...@lists.freedesktop.org; Zhang, Jerry <jerry.zh...@amd.com>; Huan,
> Alvin <alvin.h...@amd.com>; Huang, Ray <ray.hu...@amd.com>
> Subject: Re: drm/amd/powerplay: expose max engine and memory clock
> info for powerplay enabled case
gt; Cc: Zhang, Jerry <jerry.zh...@amd.com>; Huan, Alvin <alvin.h...@amd.com>;
> Quan, Evan <evan.q...@amd.com>; Huang, Ray <ray.hu...@amd.com>
> Subject: RE: drm/amd/powerplay: expose max engine and memory clock info for
> powerplay enabled case
>
>
>
Zhang, Jerry <jerry.zh...@amd.com>; Huan, Alvin <alvin.h...@amd.com>; Quan,
Evan <evan.q...@amd.com>; Huang, Ray <ray.hu...@amd.com>
Subject: RE: drm/amd/powerplay: expose max engine and memory clock info for
powerplay enabled case
I don't know if we
I don't know if we need to add a cgs call to fill in the
max_clock_voltage_limits structure. That's mostly just leftover from radeon.
A better solution would be use the existing amdgpu_dpm_get_sclk and
amdgpu_dpm_get_mclk macros. Maybe something like the attached patch? Unless
there is a
