drm/tegra: Set static Fmax for suspend frequency

The suspend_freq is a fixed value for devfreq core, while the
resume_freq will be changed dynamically based on the last previous
updated frequency value of the device.

When device is put into suspend mode, devfreq core will update the
resume frequency with the suspend frequency. Therefore, when the device
is resumed back again, it will run at suspend_freq.

Forcelly set the suspend_freq as Fmax so that device will run at Fmax
when it is resumed back.

Bug 4269900

Signed-off-by: Johnny Liu <johnliu@nvidia.com>
Change-Id: Ic6511613ae5d02831a66dd1c2a93f21c142bf3a7
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nv-oot/+/2973229
Reviewed-by: Mikko Perttunen <mperttunen@nvidia.com>
GVS: Gerrit_Virtual_Submit <buildbot_gerritrpt@nvidia.com>
This commit is contained in:
Johnny Liu
2023-09-04 04:23:51 +00:00
committed by mobile promotions
parent c9dae14cce
commit 8b99f1f5b8
4 changed files with 4 additions and 8 deletions

View File

@@ -289,8 +289,7 @@ static int nvdec_devfreq_init(struct nvdec *nvdec)
if (IS_ERR(devfreq))
return PTR_ERR(devfreq);
devfreq->suspend_freq = min_rate;
devfreq->resume_freq = max_rate;
devfreq->suspend_freq = max_rate;
nvdec->devfreq = devfreq;
return 0;