diff options
| author | Thomas Fleury <tfleury@nvidia.com> | 2017-04-11 16:43:24 -0400 |
|---|---|---|
| committer | mobile promotions <svcmobile_promotions@nvidia.com> | 2017-04-18 19:14:49 -0400 |
| commit | f4e36283437ff5dfcac08205aa994c62d95e1d21 (patch) | |
| tree | 0f8df44fe8551edab0fac94c850aac34724a2be5 /drivers/gpu/nvgpu/pmgr | |
| parent | 03e7ef2657b4de22eff521b3e44fc4ed5cdf4dca (diff) | |
gpu: nvgpu: clip target frequencies in arbiter
It is currently possible to set GPCCLK lower than the
minimum allowed frequency.
Clip target GPCCLK/MCLK according to valid min/max range
in arbiter. We could do this before submitting request to
arbiter, but then we would loose information on the
requested target frequency. Instead, we cache the clock
range in arbiter context, and check target frequency when
running arbiter.
Bug 200288036
Change-Id: I29f5176e6365a926d1041430c05a63f0c8447e2b
Reviewed-on: http://git-master/r/1460834
(cherry picked from commit eb626903e4fc046fe1f0eaee703c857e9a0f2b4d)
Signed-off-by: Thomas Fleury <tfleury@nvidia.com>
Reviewed-on: http://git-master/r/1461715
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Diffstat (limited to 'drivers/gpu/nvgpu/pmgr')
0 files changed, 0 insertions, 0 deletions