On Wed, Jul 04, 2012 at 09:52:11AM +0200, Daniel Vetter wrote:
> On Tue, Jul 03, 2012 at 02:16:42PM -0700, Stéphane Marchesin wrote:
> > The up and down thresholds are very asymetric, so it is possible
> > to have a case where a spike of rendering increases the GPU clock to
> > the max (because the up threshold is low) and then a simple blinking
> > cursor is enough to keep the clock at the maximum speed forever
> > (because the down threshold is high).
> >
> > Lowering the down threshold allows the GPU clock to go back down even
> > when there is a blinking cursor on the screen.
> >
> > Signed-off-by: Stéphane Marchesin <
marcheu@chromium.org>
>
> I've just merged Eugeni's hsw rc6 patches - those contain newly tuning
> variables. Can you maybe try out whether these would have the same effect?
> I'd prefer to simple enable these, presuming that the hw guys we've got
> them from did some decent tuning ...