diff options
| author | Thomas Fleury <tfleury@nvidia.com> | 2018-06-27 20:15:26 -0400 |
|---|---|---|
| committer | mobile promotions <svcmobile_promotions@nvidia.com> | 2018-07-01 10:03:03 -0400 |
| commit | 1691c34a6860eb746894d495eb39b25010a92826 (patch) | |
| tree | 2f336c0456e3dd85a865f66d940cfd349aa63fc4 /drivers/gpu/nvgpu/gp106 | |
| parent | cd7c4331453af7751a19bd96150715b86b8ca2ca (diff) | |
gpu: nvgpu: adjust gpc2clk to nearest V/f point
When requesting a gpc2clck below lowest V/f point, clock arbiter
did not properly adjust target value to nearest V/f point. This
could lead to lower than expected effective frequency. Fixed the
logic to adjust to nearest V/f point.
Bug 200412996
Change-Id: I36c24b4c081931e2ac54da14d49e46fcb14503e3
(cherry picked from commit 7ed1f8fb39f76208922daa91d00905cdb96b2304)
Signed-off-by: Thomas Fleury <tfleury@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1763641
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Vijayakumar Subbu <vsubbu@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Diffstat (limited to 'drivers/gpu/nvgpu/gp106')
0 files changed, 0 insertions, 0 deletions