Quoting Kristian Høgsberg (2018-02-01 20:22:40) > On Thu, Feb 1, 2018 at 9:53 AM Chris Wilson <ch...@chris-wilson.co.uk> > wrote: > > > Quoting Andy Lutomirski (2018-02-01 17:40:22) > > > *However*, I do see one unfortunate side effect of turning on PSR. It > > > seems that, when I move my cursor a little bit after a few seconds of > > > doing nothing, there seems to be a little bit of lag, as if either a > > > few frames are dropped at the beginning of the motion or maybe the > > > entire motion is delayed a bit. I don't notice a similar delay when > > > typing, so I'm wondering if maybe there's a min > > or driver bug in which > > > the driver doesn't kick the panel out of PSR quite as quickly when the > > > cursor is updated as it does when the framebuffer is updated. > > > One thing that's important know regarding the cursor is whether the > > display server is using a HW cursor or SW cursor. Could you please attach > > the log from the display server (or if you are using a stock > > distribution that's probably enough to work out what it is using)? > > -Chris > > We had a similar problem for Rockchip in ChromeOS and ended up using an > input handler to let us start the PSR exit as early as possible:
Reminds me of mutter devs suggesting that we may like to kick the gpu to max clocks high frequency on any input activity as well. (I'm still not convinced that's a good idea, for mundane typing we barely need to wake up the gpu. :) I guess it all depends on expected wakeup latencies, but I didn't think PSR had multi-frame lag? -Chris _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
