diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2017-03-13 17:06:17 +0000 |
|---|---|---|
| committer | Jani Nikula <jani.nikula@intel.com> | 2017-03-14 12:29:43 +0200 |
| commit | 8f68d591d4765b2e1ce9d916ac7bc5583285c4ad (patch) | |
| tree | 5cfe7e02a2164f1cbf63bcf40e25ff6562ce80e0 /drivers/gpu/drm/drm_blend.c | |
| parent | 0f5418e564ac6452b9086295646e602a9addc4bf (diff) | |
| download | blackbird-op-linux-8f68d591d4765b2e1ce9d916ac7bc5583285c4ad.tar.gz blackbird-op-linux-8f68d591d4765b2e1ce9d916ac7bc5583285c4ad.zip | |
drm/i915: Stop using RP_DOWN_EI on Baytrail
On Baytrail, we manually calculate busyness over the evaluation interval
to avoid issues with miscaluations with RC6 enabled. However, it turns
out that the DOWN_EI interrupt generator is completely bust - it
operates in two modes, continuous or never. Neither of which are
conducive to good behaviour. Stop unmask the DOWN_EI interrupt and just
compute everything from the UP_EI which does seem to correspond to the
desired interval.
v2: Fixup gen6_rps_pm_mask() as well
v3: Inline vlv_c0_above() to combine the now identical elapsed
calculation for up/down and simplify the threshold testing
Fixes: 43cf3bf084ba ("drm/i915: Improved w/a for rps on Baytrail")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: <stable@vger.kernel.org> # v4.1+
Link: http://patchwork.freedesktop.org/patch/msgid/20170309211232.28878-1-chris@chris-wilson.co.uk
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20170313170617.31564-1-chris@chris-wilson.co.uk
(cherry picked from commit e0e8c7cb6eb68e9256de2d8cbeb481d3701c05ac)
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Diffstat (limited to 'drivers/gpu/drm/drm_blend.c')
0 files changed, 0 insertions, 0 deletions
