drm/i915: Jump to at least RPe on VLV when increasing the GPU frequency
If the current GPU frquency is below RPe, and we're asked to increase it, just go directly to RPe. This should provide better performance faster than letting the frequency trickle up in response to the up threshold interrupts. For now just do it for VLV, since that matches quite closely how VLV used to operate when the rps delayed timer kept things at RPe always. Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
This commit is contained in:
Родитель
6dc5848899
Коммит
7425034a33
|
@ -699,9 +699,17 @@ static void gen6_pm_rps_work(struct work_struct *work)
|
|||
|
||||
mutex_lock(&dev_priv->rps.hw_lock);
|
||||
|
||||
if (pm_iir & GEN6_PM_RP_UP_THRESHOLD)
|
||||
if (pm_iir & GEN6_PM_RP_UP_THRESHOLD) {
|
||||
new_delay = dev_priv->rps.cur_delay + 1;
|
||||
else
|
||||
|
||||
/*
|
||||
* For better performance, jump directly
|
||||
* to RPe if we're below it.
|
||||
*/
|
||||
if (IS_VALLEYVIEW(dev_priv->dev) &&
|
||||
dev_priv->rps.cur_delay < dev_priv->rps.rpe_delay)
|
||||
new_delay = dev_priv->rps.rpe_delay;
|
||||
} else
|
||||
new_delay = dev_priv->rps.cur_delay - 1;
|
||||
|
||||
/* sysfs frequency interfaces may have snuck in while servicing the
|
||||
|
|
Загрузка…
Ссылка в новой задаче