aboutsummaryrefslogtreecommitdiff
path: root/scripts/gdb
diff options
context:
space:
mode:
authorDaniel Vetter <[email protected]>2013-07-21 13:16:24 +0200
committerDaniel Vetter <[email protected]>2013-07-21 15:37:02 +0200
commit181d1b9e31c668259d3798c521672afb8edd355c (patch)
treec35adc77a69304b3ee622a911b3a99f40e6a75d6 /scripts/gdb
parenta7cd1b8fea2f341b626b255d9898a5ca5fabbf0a (diff)
drm/i915: fix up gt init sequence fallout
The regression fix for gen6+ rps fallout commit 7dcd2677ea912573d9ed4bcd629b0023b2d11505 Author: Konstantin Khlebnikov <[email protected]> Date: Wed Jul 17 10:22:58 2013 +0400 drm/i915: fix long-standing SNB regression in power consumption after resume unintentionally also changed the init sequence ordering between gt_init and gt_reset - we need to reset BIOS damage like leftover forcewake references before we run our own code. Otherwise we can get nasty dmesg noise like [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear. again. Since _reset suggests that we first need to have stuff initialized (which isn't the case here) call it sanitze instead. While at it also block out the rps disable introduced by the above commit on ilk: We don't have any knowledge of ilk rps being broken in similar ways. And the disable functions uses the default hw state which is only read out when we're enabling rps. So essentially we've been writing random grabage into that register. Reported-by: Chris Wilson <[email protected]> Cc: Chris Wilson <[email protected]> Cc: Konstantin Khlebnikov <[email protected]> Cc: Jesse Barnes <[email protected]> Cc: [email protected] Tested-by: Chris Wilson <[email protected]> Reviewed-by: Chris Wilson <[email protected]> Signed-off-by: Daniel Vetter <[email protected]>
Diffstat (limited to 'scripts/gdb')
0 files changed, 0 insertions, 0 deletions