[Intel-gfx] [PATCH 10/11] drm/i915: PSR Baytrail: Force exit by inactivating it.

2014-02-28 Thread Rodrigo Vivi
Baytrail cannot easily detect screen updates and force PSR exit. So we inactivate it on {busy_ioctl, set_domain, sw_finish and mark_busy} and update to enable it back it later with a delayed workqueue. Cc: Chris Wilson Cc: Ville Syrjälä Signed-off-by: Rodrigo Vivi --- drivers/gpu/drm/i915/i915

Re: [Intel-gfx] [PATCH 10/11] drm/i915: PSR Baytrail: Force exit by inactivating it.

2014-03-01 Thread Chris Wilson
On Fri, Feb 28, 2014 at 08:44:45PM -0300, Rodrigo Vivi wrote: > Baytrail cannot easily detect screen updates and force PSR exit. > So we inactivate it on {busy_ioctl, set_domain, sw_finish and mark_busy} > and update to enable it back it later with a delayed workqueue. Why are we not checking if t

Re: [Intel-gfx] [PATCH 10/11] drm/i915: PSR Baytrail: Force exit by inactivating it.

2014-03-01 Thread Rodrigo Vivi
On Sat, Mar 1, 2014 at 5:45 AM, Chris Wilson wrote: > On Fri, Feb 28, 2014 at 08:44:45PM -0300, Rodrigo Vivi wrote: >> Baytrail cannot easily detect screen updates and force PSR exit. >> So we inactivate it on {busy_ioctl, set_domain, sw_finish and mark_busy} >> and update to enable it back it lat

Re: [Intel-gfx] [PATCH 10/11] drm/i915: PSR Baytrail: Force exit by inactivating it.

2014-03-01 Thread Rodrigo Vivi
On Sat, Mar 1, 2014 at 5:45 AM, Chris Wilson wrote: > On Fri, Feb 28, 2014 at 08:44:45PM -0300, Rodrigo Vivi wrote: >> Baytrail cannot easily detect screen updates and force PSR exit. >> So we inactivate it on {busy_ioctl, set_domain, sw_finish and mark_busy} >> and update to enable it back it lat

Re: [Intel-gfx] [PATCH 10/11] drm/i915: PSR Baytrail: Force exit by inactivating it.

2014-03-01 Thread Chris Wilson
On Sat, Mar 01, 2014 at 03:29:41PM -0300, Rodrigo Vivi wrote: > On Sat, Mar 1, 2014 at 5:45 AM, Chris Wilson wrote: > > On Fri, Feb 28, 2014 at 08:44:45PM -0300, Rodrigo Vivi wrote: > >> Baytrail cannot easily detect screen updates and force PSR exit. > >> So we inactivate it on {busy_ioctl, set_d

Re: [Intel-gfx] [PATCH 10/11] drm/i915: PSR Baytrail: Force exit by inactivating it.

2014-03-03 Thread Rodrigo Vivi
On Sat, Mar 1, 2014 at 6:10 PM, Chris Wilson wrote: > On Sat, Mar 01, 2014 at 03:29:41PM -0300, Rodrigo Vivi wrote: >> On Sat, Mar 1, 2014 at 5:45 AM, Chris Wilson >> wrote: >> > On Fri, Feb 28, 2014 at 08:44:45PM -0300, Rodrigo Vivi wrote: >> >> Baytrail cannot easily detect screen updates and

Re: [Intel-gfx] [PATCH 10/11] drm/i915: PSR Baytrail: Force exit by inactivating it.

2014-03-05 Thread Daniel Vetter
On Mon, Mar 03, 2014 at 01:09:36PM -0300, Rodrigo Vivi wrote: > On Sat, Mar 1, 2014 at 6:10 PM, Chris Wilson wrote: > > On Sat, Mar 01, 2014 at 03:29:41PM -0300, Rodrigo Vivi wrote: > >> On Sat, Mar 1, 2014 at 5:45 AM, Chris Wilson > >> wrote: > >> > On Fri, Feb 28, 2014 at 08:44:45PM -0300, Rod

Re: [Intel-gfx] [PATCH 10/11] drm/i915: PSR Baytrail: Force exit by inactivating it.

2014-03-12 Thread Rodrigo Vivi
On Wed, Mar 5, 2014 at 2:46 PM, Daniel Vetter wrote: > On Mon, Mar 03, 2014 at 01:09:36PM -0300, Rodrigo Vivi wrote: >> On Sat, Mar 1, 2014 at 6:10 PM, Chris Wilson >> wrote: >> > On Sat, Mar 01, 2014 at 03:29:41PM -0300, Rodrigo Vivi wrote: >> >> On Sat, Mar 1, 2014 at 5:45 AM, Chris Wilson >

Re: [Intel-gfx] [PATCH 10/11] drm/i915: PSR Baytrail: Force exit by inactivating it.

2014-03-12 Thread Daniel Vetter
On Wed, Mar 12, 2014 at 6:11 PM, Rodrigo Vivi wrote: >> We have it, it's called dirtyfb. But we need to keep the current userspace >> stuff mostly working first, hence all this trouble. We can fix the gtt >> trouble with a delayed work (one vblank or so) which >> a) does a psr_exit >> b) shots dow