Message ID | 1376613069-15790-16-git-send-email-james.ausmus@intel.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On Thu, Aug 15, 2013 at 05:30:40PM -0700, james.ausmus@intel.com wrote: > From: Stéphane Marchesin <marcheu@chromium.org> > > The thresholds for GPU reclocking are highly asymetrical. This creates an > interesting phenomenon on Chrome startup where the clock ramps up very > quickly, and then the blinking cursor is enough to keep it up. Obviously > having the max GPU clock on the login screen is very bad for thermals. > > With this change, the clock goes back to its minimum frequency after a couple > of seconds. You can drop the RPS changes as Stéphane has been feeding these back once he found (semi?) stable values. -Chris
diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c index 3280cff..6d5e3ed 100644 --- a/drivers/gpu/drm/i915/intel_pm.c +++ b/drivers/gpu/drm/i915/intel_pm.c @@ -2612,7 +2612,7 @@ static void gen6_enable_rps(struct drm_device *dev) dev_priv->rps.min_delay << 16); I915_WRITE(GEN6_RP_UP_THRESHOLD, 59400); - I915_WRITE(GEN6_RP_DOWN_THRESHOLD, 245000); + I915_WRITE(GEN6_RP_DOWN_THRESHOLD, 100000); I915_WRITE(GEN6_RP_UP_EI, 66000); I915_WRITE(GEN6_RP_DOWN_EI, 350000);