drm/i915: Update rps interrupt limits
Subsystems (2)
PATCH 1/1 drm/i915: Update rps interrupt limits
From: Jeff McGee <[email protected]>
This bug was found on OTC Haswell Android product which makes use of sysfs to set rps min and max range at boot.
This patch follows the original patch in implementing the fix with a minimum of code change, which was desirable for late stage product. A cleaner fix might involve refactoring the rps interface a bit by perhaps making gen6_rps_limits a public function that could be called from debugfs with the desired min/max. And the register update could be placed in that function. Let me know if something like that is more desirable for upstream and provide any thoughts on form.
I also noticed that writing the interrupt limits register has been removed for Valleyview recently by Chris Wilson, so I have removed those parts of the original patch. I guess that means that it is not relevant for Valleyview?
Jeff McGee (1):
drm/i915: Update rps interrupt limits
drivers/gpu/drm/i915/i915_sysfs.c | 10 ++++++++++ drivers/gpu/drm/i915/intel_pm.c | 10 +++++++++- 2 files changed, 19 insertions(+), 1 deletion(-)
Signature · 1 line
1.8.4.2
PATCH 1/1 drm/i915: Update rps interrupt limits
From: Jeff McGee <[email protected]>
sysfs changes to rps min and max delay were only triggering an update of the rps interrupt limits if the active delay required an update. This change ensures that interrupt limits are always updated.
OTC-Tracker: VIZ-3144
--- drivers/gpu/drm/i915/i915_sysfs.c | 10 ++++++++++ drivers/gpu/drm/i915/intel_pm.c | 10 +++++++++- 2 files changed, 19 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/i915_sysfs.c +10 -0
@@ -349,6 +349,11 @@ static ssize_t gt_max_freq_mhz_store(struct device *kdev,else gen6_set_rps (dev, val); } +else if (!IS_VALLEYVIEW (dev)) +/* We still need gen6_set_rps to process the new max_delay +and update the interrupt limits even though frequency +request is unchanged. */ +gen6_set_rps (dev, dev_priv->rps.cur_delay);mutex_unlock (&dev_priv->rps.hw_lock);
@@ -418,6 +423,11 @@ static ssize_t gt_min_freq_mhz_store(struct device *kdev,else gen6_set_rps (dev, val); } +else if (!IS_VALLEYVIEW (dev)) +/* We still need gen6_set_rps to process the new min_delay +and update the interrupt limits even though frequency +request is unchanged. */ +gen6_set_rps (dev, dev_priv->rps.cur_delay);mutex_unlock (&dev_priv->rps.hw_lock);
drivers/gpu/drm/i915/intel_pm.c +9 -1
@@ -3538,6 +3538,9 @@ static void gen6_set_rps_thresholds(struct drm_i915_private *dev_priv, u8 val) dev_priv->rps.last_adj =0 ; } +/* gen6_set_rps is called to update the frequency request, but should also be +* called when the range (min_delay and max_delay) is modified so that we can +* update the GEN6_RP_INTERRUPT_LIMITS register accordingly. */ void gen6_set_rps (struct drm_device *dev,u8 val) {struct drm_i915_private *dev_priv = dev->dev_private;
@@ -3546,8 +3549,13 @@ void gen6_set_rps(struct drm_device *dev, u8 val)WARN_ON (val > dev_priv->rps.max_delay);WARN_ON (val < dev_priv->rps.min_delay); -if (val == dev_priv->rps.cur_delay) +if (val == dev_priv->rps.cur_delay) { +/* min/max delay may still have been modified so be sure to +* write the limits value */ +I915_WRITE (GEN6_RP_INTERRUPT_LIMITS , limits); +return ; + }gen6_set_rps_thresholds (dev_priv, val);
Signature · 1 line
1.8.4.2
PATCH v2 1/1 drm/i915: Update rps interrupt limits
From: Jeff McGee <[email protected]>
sysfs changes to rps min and max delay were only triggering an update of the rps interrupt limits if the active delay required an update. This change ensures that interrupt limits are always updated.
v2: correct compile issue missed on rebase
OTC-Tracker: VIZ-3144
--- drivers/gpu/drm/i915/i915_sysfs.c | 10 ++++++++++ drivers/gpu/drm/i915/intel_pm.c | 11 ++++++++++- 2 files changed, 20 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/i915_sysfs.c +10 -0
@@ -349,6 +349,11 @@ static ssize_t gt_max_freq_mhz_store(struct device *kdev,else gen6_set_rps (dev, val); } +else if (!IS_VALLEYVIEW (dev)) +/* We still need gen6_set_rps to process the new max_delay +and update the interrupt limits even though frequency +request is unchanged. */ +gen6_set_rps (dev, dev_priv->rps.cur_delay);mutex_unlock (&dev_priv->rps.hw_lock);
@@ -418,6 +423,11 @@ static ssize_t gt_min_freq_mhz_store(struct device *kdev,else gen6_set_rps (dev, val); } +else if (!IS_VALLEYVIEW (dev)) +/* We still need gen6_set_rps to process the new min_delay +and update the interrupt limits even though frequency +request is unchanged. */ +gen6_set_rps (dev, dev_priv->rps.cur_delay);mutex_unlock (&dev_priv->rps.hw_lock);
drivers/gpu/drm/i915/intel_pm.c +10 -1
@@ -3538,6 +3538,9 @@ static void gen6_set_rps_thresholds(struct drm_i915_private *dev_priv, u8 val) dev_priv->rps.last_adj =0 ; } +/* gen6_set_rps is called to update the frequency request, but should also be +* called when the range (min_delay and max_delay) is modified so that we can +* update the GEN6_RP_INTERRUPT_LIMITS register accordingly. */ void gen6_set_rps (struct drm_device *dev,u8 val) {struct drm_i915_private *dev_priv = dev->dev_private;
@@ -3546,8 +3549,14 @@ void gen6_set_rps(struct drm_device *dev, u8 val)WARN_ON (val > dev_priv->rps.max_delay);WARN_ON (val < dev_priv->rps.min_delay); -if (val == dev_priv->rps.cur_delay) +if (val == dev_priv->rps.cur_delay) { +/* min/max delay may still have been modified so be sure to +* write the limits value */ +I915_WRITE (GEN6_RP_INTERRUPT_LIMITS , +gen6_rps_limits (dev_priv, val)); +return ; + }gen6_set_rps_thresholds (dev_priv, val);
Signature · 1 line
1.8.4.2
Quoted 5 lines · On Tue, Nov 12, 2013 at 03:04:48PM -0600, [email protected] wrote:
From: Jeff McGee <[email protected]>
sysfs changes to rps min and max delay were only triggering an update of the rps interrupt limits if the active delay required an update. This change ensures that interrupt limits are always updated.
So this means that e.g. if we set the limit to 600MHz and the gpu runs at that, and then we increase it to 800MHz or, then we'll never get the up interrupt?
If that's the case then I think we should add subtests to the "does rps still work" testcase from the earlier patch for resetting rps after a gpu hang. Which means a behavioural test like I've suggested (instead of just checking register values like Jesse suggested) sounds like the better approach.
Looks like you guys are the only ones actually changing the limits at runtime ;-)
-Daniel
Quoted 76 lines
v2: correct compile issue missed on rebase
OTC-Tracker: VIZ-3144
Change-Id I0adb8d968190e138382b449dcec7e297743b9ccaSigned-off-by Jeff McGee <[email protected]>--- drivers/gpu/drm/i915/i915_sysfs.c | 10 ++++++++++ drivers/gpu/drm/i915/intel_pm.c | 11 ++++++++++- 2 files changed, 20 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/i915_sysfs.c +10
-0@@ -349,6 +349,11 @@ static ssize_t gt_max_freq_mhz_store(struct device *kdev,else gen6_set_rps (dev, val); } +else if (!IS_VALLEYVIEW (dev)) +/* We still need gen6_set_rps to process the new max_delay +and update the interrupt limits even though frequency +request is unchanged. */ +gen6_set_rps (dev, dev_priv->rps.cur_delay);mutex_unlock (&dev_priv->rps.hw_lock);@@ -418,6 +423,11 @@ static ssize_t gt_min_freq_mhz_store(struct device *kdev,else gen6_set_rps (dev, val); } +else if (!IS_VALLEYVIEW (dev)) +/* We still need gen6_set_rps to process the new min_delay +and update the interrupt limits even though frequency +request is unchanged. */ +gen6_set_rps (dev, dev_priv->rps.cur_delay);mutex_unlock (&dev_priv->rps.hw_lock);drivers/gpu/drm/i915/intel_pm.c +10
-1@@ -3538,6 +3538,9 @@ static void gen6_set_rps_thresholds(struct drm_i915_private *dev_priv, u8 val) dev_priv->rps.last_adj =0 ; } +/* gen6_set_rps is called to update the frequency request, but should also be +* called when the range (min_delay and max_delay) is modified so that we can +* update the GEN6_RP_INTERRUPT_LIMITS register accordingly. */ void gen6_set_rps (struct drm_device *dev,u8 val) {struct drm_i915_private *dev_priv = dev->dev_private;@@ -3546,8 +3549,14 @@ void gen6_set_rps(struct drm_device *dev, u8 val)WARN_ON (val > dev_priv->rps.max_delay);WARN_ON (val < dev_priv->rps.min_delay); -if (val == dev_priv->rps.cur_delay) +if (val == dev_priv->rps.cur_delay) { +/* min/max delay may still have been modified so be sure to +* write the limits value */ +I915_WRITE (GEN6_RP_INTERRUPT_LIMITS , +gen6_rps_limits (dev_priv, val)); +return ; + }gen6_set_rps_thresholds (dev_priv, val);Signature · 6 lines
1.8.4.2 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
PATCH v3 1/1 drm/i915: Update rps interrupt limits
From: Jeff McGee <[email protected]>
sysfs changes to rps min and max delay were only triggering an update of the rps interrupt limits if the active delay required an update. This change ensures that interrupt limits are always updated.
v2: correct compile issue missed on rebase
v3: add igt testcases to signed-off-by section
Testcase: igt/pm_rps/min-max-config-idle
Testcase: igt/pm_rps/min-max-config-loaded
--- drivers/gpu/drm/i915/i915_sysfs.c | 10 ++++++++++ drivers/gpu/drm/i915/intel_pm.c | 11 ++++++++++- 2 files changed, 20 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/i915_sysfs.c +10 -0
@@ -357,6 +357,11 @@ static ssize_t gt_max_freq_mhz_store(struct device *kdev,else gen6_set_rps (dev, val); } +else if (!IS_VALLEYVIEW (dev)) +/* We still need gen6_set_rps to process the new max_delay +and update the interrupt limits even though frequency +request is unchanged. */ +gen6_set_rps (dev, dev_priv->rps.cur_delay);mutex_unlock (&dev_priv->rps.hw_lock);
@@ -426,6 +431,11 @@ static ssize_t gt_min_freq_mhz_store(struct device *kdev,else gen6_set_rps (dev, val); } +else if (!IS_VALLEYVIEW (dev)) +/* We still need gen6_set_rps to process the new min_delay +and update the interrupt limits even though frequency +request is unchanged. */ +gen6_set_rps (dev, dev_priv->rps.cur_delay);mutex_unlock (&dev_priv->rps.hw_lock);
drivers/gpu/drm/i915/intel_pm.c +10 -1
@@ -3003,6 +3003,9 @@ static void gen6_set_rps_thresholds(struct drm_i915_private *dev_priv, u8 val) dev_priv->rps.last_adj =0 ; } +/* gen6_set_rps is called to update the frequency request, but should also be +* called when the range (min_delay and max_delay) is modified so that we can +* update the GEN6_RP_INTERRUPT_LIMITS register accordingly. */ void gen6_set_rps (struct drm_device *dev,u8 val) {struct drm_i915_private *dev_priv = dev->dev_private;
@@ -3011,8 +3014,14 @@ void gen6_set_rps(struct drm_device *dev, u8 val)WARN_ON (val > dev_priv->rps.max_delay);WARN_ON (val < dev_priv->rps.min_delay); -if (val == dev_priv->rps.cur_delay) +if (val == dev_priv->rps.cur_delay) { +/* min/max delay may still have been modified so be sure to +* write the limits value */ +I915_WRITE (GEN6_RP_INTERRUPT_LIMITS , +gen6_rps_limits (dev_priv, val)); +return ; + }gen6_set_rps_thresholds (dev_priv, val);
Signature · 1 line
1.8.5.2
Daniel Vetter
AppliedQuoted 6 lines · On Tue, Feb 04, 2014 at 11:37:01AM -0600, [email protected] wrote:
From: Jeff McGee <[email protected]>
sysfs changes to rps min and max delay were only triggering an update of the rps interrupt limits if the active delay required an update. This change ensures that interrupt limits are always updated.
Quoted 6 lines
v2: correct compile issue missed on rebase
v3: add igt testcases to signed-off-by sectionTestcase: igt/pm_rps/min-max-config-idle
Testcase: igt/pm_rps/min-max-config-loadedSigned-off-by Jeff McGee <[email protected]>
Queued for -next, thanks for the patch.
-Daniel
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch