On Thu, May 15, 2014 at 08:13:05PM -0400, Rodrigo Vivi wrote: > The perfect solution for psr_exit is the hardware tracking the changes and > doing the psr exit by itself. This scenario works for HSW and BDW with some > environments like Gnome and Wayland. > > However there are many other scenarios that this isn't true. Mainly one right > now is KDE users on HSW and BDW with PSR on. User would miss many screen > updates. For instances any key typed could be seen only when mouse cursor is > moved. So this patch introduces the ability of trigger PSR exit on kernel side > on some common cases that. > > Most of the cases are coverred by psr_exit at set_domain. The remaining cases > are coverred by triggering it at set_domain, busy_ioctl, sw_finish and > mark_busy. > > The downside here might be reducing the residency time on the cases this > already work very wall like Gnome environment. But so far let's get focused > on fixinge issues sio PSR couild be used for everybody and we could even > get it enabled by default. Later we can add some alternatives to choose the > level of PSR efficiency over boot flag of even over crtc property. What happened to the front buffer tracking? -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
