1. Fix intel_cleanup_ring_buffer() to handle the error cleanup case where
the ringbuffer has been allocated but map-and-pin failed. Unpin it iff
it's previously been mapped-and-pinned.
2. Fix the error path in intel_init_ring_buffer(), which already called
intel_destroy_ringbuffer_obj(),
In legacy ringbuffer mode, the HWSP is a separate GEM object with
its own pinning and reference counts. In LRC mode, however, it's not;
instead its part of the default context object. The LRC-mode setup &
teardown code therefore needs to handle this specially; the presence
of the two bugs just fixe
The kunmap() call here didn't match the corresponding kmap().
The kmapping was changed with the introduction of the GuC-compatible
layout of context objects and the introduction of "LRC_PPHWSP_PN", in
d167519 drm/i915: Integrate GuC-based command submission
but the corresponding kunmap() wasn
From: Alex Dai
Previously GuC uses ring id as engine id because of same definition.
But this is not true since this commit:
commit de1add360522c876c25ef2ab1c94bdb509ab
Author: Tvrtko Ursulin
Date: Fri Jan 15 15:12:50 2016 +
drm/i915: Decouple execbuf uAPI from internal implementa
From: Abhay Kumar
Make resume/on codepath not to wait for panel_power_cycle_delay(t11_t12)
if this time is already spent in suspend/poweron time.
v2: Use CLOCK_BOOTTIME and remove jiffies for panel power cycle
delay calculation(Ville).
v3: Addressed below comments
1. Tracking time from
== Summary ==
Built on 8fe9e785ae04fa7c37f7935cff12d62e38054b60 drm-intel-nightly:
2016y-01m-21d-11h-02m-42s UTC integration manifest
Test kms_flip:
Subgroup basic-flip-vs-dpms:
pass -> DMESG-WARN (ilk-hp8440p)
Subgroup basic-flip-vs-modeset:
== Summary ==
Built on 8fe9e785ae04fa7c37f7935cff12d62e38054b60 drm-intel-nightly:
2016y-01m-21d-11h-02m-42s UTC integration manifest
bdw-nuci7total:140 pass:131 dwarn:0 dfail:0 fail:0 skip:9
bdw-ultratotal:143 pass:137 dwarn:0 dfail:0 fail:0 skip:6
bsw-nuc-2
101 - 107 of 107 matches
Mail list logo
