On Fri, Sep 27, 2019 at 10:41:43AM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 17.09.19 um 15:06 schrieb Daniel Vetter:
> > On Thu, Sep 12, 2019 at 08:42:28AM +0200, Thomas Zimmermann wrote:
> > > Before updating the display from the console's shadow buffer, the dirty
> > > worker now waits for vb
Hi
Am 17.09.19 um 15:06 schrieb Daniel Vetter:
On Thu, Sep 12, 2019 at 08:42:28AM +0200, Thomas Zimmermann wrote:
Before updating the display from the console's shadow buffer, the dirty
worker now waits for vblank. This allows several screen updates to pile
up and acts as a rate limiter.
v2:
On Thu, Sep 12, 2019 at 08:42:28AM +0200, Thomas Zimmermann wrote:
> Before updating the display from the console's shadow buffer, the dirty
> worker now waits for vblank. This allows several screen updates to pile
> up and acts as a rate limiter.
>
> v2:
> * don't hold helper->lock while wa
On Thu, Sep 12, 2019 at 08:42:28AM +0200, Thomas Zimmermann wrote:
> Before updating the display from the console's shadow buffer, the dirty
> worker now waits for vblank. This allows several screen updates to pile
> up and acts as a rate limiter.
>
> v2:
> * don't hold helper->lock while wa
Before updating the display from the console's shadow buffer, the dirty
worker now waits for vblank. This allows several screen updates to pile
up and acts as a rate limiter.
v2:
* don't hold helper->lock while waiting for vblank
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/drm_
