mirror of
git://nv-tegra.nvidia.com/linux-nvgpu.git
synced 2025-12-22 09:12:24 +03:00
d664ff12af
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 Signed-off-by: Thomas Fleury <tfleury@nvidia.com> (cherry picked from commit eb626903e4fc046fe1f0eaee703c857e9a0f2b4d) Reviewed-on: http://git-master/r/1461882 (cherry picked from commit 3615061045276c8913057e1c0e8cc443b70d2ad9) Reviewed-on: http://git-master/r/1467627 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: svccoveritychecker <svccoveritychecker@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: Vladislav Buzov <vbuzov@nvidia.com>