[Intel-gfx] [PATCH v2] drm/i915: Removed the read of RP_STATE_CAP from sysfs/debugfs functions

2015-02-26 Thread akash . goel
From: Akash Goel 

The frequency values(Rp0, Rp1, Rpn) reported by RP_STATE_CAP register
are stored, initially by the Driver, inside the dev_priv->rps structure.
Since these values are expected to remain same throughout, there is no real
need to read this register, on dynamic basis, from certain debugfs/sysfs
functions and the values can be instead retrieved from the dev_priv->rps
structure when needed.
For the i915_frequency_info debugfs interface, the frequency values from the
RP_STATE_CAP register only should be used, to indicate the actual Hw state,
since it is principally used for the debugging purpose.

v2: Reverted the changes in i915_frequency_info function, to continue report
back the frequency values, as per the actual Hw state (Chris)

Signed-off-by: Akash Goel 
---
 drivers/gpu/drm/i915/i915_debugfs.c | 32 --
 drivers/gpu/drm/i915/i915_sysfs.c   | 39 +
 2 files changed, 17 insertions(+), 54 deletions(-)

diff --git a/drivers/gpu/drm/i915/i915_debugfs.c 
b/drivers/gpu/drm/i915/i915_debugfs.c
index 26e9c7b..3e1e5d3 100644
--- a/drivers/gpu/drm/i915/i915_debugfs.c
+++ b/drivers/gpu/drm/i915/i915_debugfs.c
@@ -4191,7 +4191,7 @@ i915_max_freq_set(void *data, u64 val)
 {
struct drm_device *dev = data;
struct drm_i915_private *dev_priv = dev->dev_private;
-   u32 rp_state_cap, hw_max, hw_min;
+   u32 hw_max, hw_min;
int ret;
 
if (INTEL_INFO(dev)->gen < 6)
@@ -4208,18 +4208,10 @@ i915_max_freq_set(void *data, u64 val)
/*
 * Turbo will still be enabled, but won't go above the set value.
 */
-   if (IS_VALLEYVIEW(dev)) {
-   val = intel_freq_opcode(dev_priv, val);
+   val = intel_freq_opcode(dev_priv, val);
 
-   hw_max = dev_priv->rps.max_freq;
-   hw_min = dev_priv->rps.min_freq;
-   } else {
-   val = intel_freq_opcode(dev_priv, val);
-
-   rp_state_cap = I915_READ(GEN6_RP_STATE_CAP);
-   hw_max = dev_priv->rps.max_freq;
-   hw_min = (rp_state_cap >> 16) & 0xff;
-   }
+   hw_max = dev_priv->rps.max_freq;
+   hw_min = dev_priv->rps.min_freq;
 
if (val < hw_min || val > hw_max || val < 
dev_priv->rps.min_freq_softlimit) {
mutex_unlock(&dev_priv->rps.hw_lock);
@@ -4266,7 +4258,7 @@ i915_min_freq_set(void *data, u64 val)
 {
struct drm_device *dev = data;
struct drm_i915_private *dev_priv = dev->dev_private;
-   u32 rp_state_cap, hw_max, hw_min;
+   u32 hw_max, hw_min;
int ret;
 
if (INTEL_INFO(dev)->gen < 6)
@@ -4283,18 +4275,10 @@ i915_min_freq_set(void *data, u64 val)
/*
 * Turbo will still be enabled, but won't go below the set value.
 */
-   if (IS_VALLEYVIEW(dev)) {
-   val = intel_freq_opcode(dev_priv, val);
+   val = intel_freq_opcode(dev_priv, val);
 
-   hw_max = dev_priv->rps.max_freq;
-   hw_min = dev_priv->rps.min_freq;
-   } else {
-   val = intel_freq_opcode(dev_priv, val);
-
-   rp_state_cap = I915_READ(GEN6_RP_STATE_CAP);
-   hw_max = dev_priv->rps.max_freq;
-   hw_min = (rp_state_cap >> 16) & 0xff;
-   }
+   hw_max = dev_priv->rps.max_freq;
+   hw_min = dev_priv->rps.min_freq;
 
if (val < hw_min || val > hw_max || val > 
dev_priv->rps.max_freq_softlimit) {
mutex_unlock(&dev_priv->rps.hw_lock);
diff --git a/drivers/gpu/drm/i915/i915_sysfs.c 
b/drivers/gpu/drm/i915/i915_sysfs.c
index cdc9da0..186ab95 100644
--- a/drivers/gpu/drm/i915/i915_sysfs.c
+++ b/drivers/gpu/drm/i915/i915_sysfs.c
@@ -487,38 +487,17 @@ static ssize_t gt_rp_mhz_show(struct device *kdev, struct 
device_attribute *attr
struct drm_minor *minor = dev_to_drm_minor(kdev);
struct drm_device *dev = minor->dev;
struct drm_i915_private *dev_priv = dev->dev_private;
-   u32 val, rp_state_cap;
-   ssize_t ret;
-
-   ret = mutex_lock_interruptible(&dev->struct_mutex);
-   if (ret)
-   return ret;
-   intel_runtime_pm_get(dev_priv);
-   rp_state_cap = I915_READ(GEN6_RP_STATE_CAP);
-   intel_runtime_pm_put(dev_priv);
-   mutex_unlock(&dev->struct_mutex);
+   u32 val;
 
-   if (attr == &dev_attr_gt_RP0_freq_mhz) {
-   if (IS_VALLEYVIEW(dev))
-   val = intel_gpu_freq(dev_priv, dev_priv->rps.rp0_freq);
-   else
-   val = intel_gpu_freq(dev_priv,
-((rp_state_cap & 0xff) >> 0));
-   } else if (attr == &dev_attr_gt_RP1_freq_mhz) {
-   if (IS_VALLEYVIEW(dev))
-   val = intel_gpu_freq(dev_priv, dev_priv->rps.rp1_freq);
-   else
-   val = intel_gpu_freq(dev_priv,
-((rp_state_cap & 0x00ff00) >> 8))

Re: [Intel-gfx] [PATCH v2] drm/i915: Removed the read of RP_STATE_CAP from sysfs/debugfs functions

2015-02-26 Thread Chris Wilson
On Thu, Feb 26, 2015 at 04:09:47PM +0530, akash.g...@intel.com wrote:
> From: Akash Goel 
> 
> The frequency values(Rp0, Rp1, Rpn) reported by RP_STATE_CAP register
> are stored, initially by the Driver, inside the dev_priv->rps structure.
> Since these values are expected to remain same throughout, there is no real
> need to read this register, on dynamic basis, from certain debugfs/sysfs
> functions and the values can be instead retrieved from the dev_priv->rps
> structure when needed.
> For the i915_frequency_info debugfs interface, the frequency values from the
> RP_STATE_CAP register only should be used, to indicate the actual Hw state,
> since it is principally used for the debugging purpose.
> 
> v2: Reverted the changes in i915_frequency_info function, to continue report
> back the frequency values, as per the actual Hw state (Chris)
> 
> Signed-off-by: Akash Goel 
Nice improvement,
Reviewed-by: Chris Wilson 
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] [PATCH v2] drm/i915: Removed the read of RP_STATE_CAP from sysfs/debugfs functions

2015-02-26 Thread Daniel Vetter
On Thu, Feb 26, 2015 at 10:38:28AM +, Chris Wilson wrote:
> On Thu, Feb 26, 2015 at 04:09:47PM +0530, akash.g...@intel.com wrote:
> > From: Akash Goel 
> > 
> > The frequency values(Rp0, Rp1, Rpn) reported by RP_STATE_CAP register
> > are stored, initially by the Driver, inside the dev_priv->rps structure.
> > Since these values are expected to remain same throughout, there is no real
> > need to read this register, on dynamic basis, from certain debugfs/sysfs
> > functions and the values can be instead retrieved from the dev_priv->rps
> > structure when needed.
> > For the i915_frequency_info debugfs interface, the frequency values from the
> > RP_STATE_CAP register only should be used, to indicate the actual Hw state,
> > since it is principally used for the debugging purpose.
> > 
> > v2: Reverted the changes in i915_frequency_info function, to continue report
> > back the frequency values, as per the actual Hw state (Chris)
> > 
> > Signed-off-by: Akash Goel 
> Nice improvement,
> Reviewed-by: Chris Wilson 

Queued for -next, thanks for the patch.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] [PATCH v2] drm/i915: Removed the read of RP_STATE_CAP from sysfs/debugfs functions

2015-02-27 Thread shuang . he
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: 
shuang...@intel.com)
Task id: 5834
-Summary-
Platform  Delta  drm-intel-nightly  Series Applied
PNV -1  282/282  281/282
ILK  308/308  308/308
SNB -1  326/326  325/326
IVB  379/379  379/379
BYT  294/294  294/294
HSW -1  387/387  386/387
BDW -1  316/316  315/316
-Detailed-
Platform  Testdrm-intel-nightly  Series 
Applied
 PNV  igt_gem_userptr_blits_minor-unsync-normal  DMESG_WARN(1)PASS(1)  
DMESG_WARN(1)PASS(1)
*SNB  igt_kms_plane_plane-position-hole-pipe-B-plane-1  PASS(3)  
TIMEOUT(1)PASS(1)
*HSW  igt_gem_storedw_batches_loop_normal  PASS(2)  DMESG_WARN(1)PASS(1)
*BDW  igt_gem_gtt_hog  PASS(5)  DMESG_WARN(1)PASS(1)
Note: You need to pay more attention to line start with '*'
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx