On Mon, Jul 16, 2012 at 12:50 PM, Daniel Vetter wrote:
> 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
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
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
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 h
