[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 2 Feb 2022 10:45:42 +0100
From: Noralf Trønnes <noralf@...nnes.org>
To: Thomas Zimmermann <tzimmermann@...e.de>,
Sam Ravnborg <sam@...nborg.org>,
Javier Martinez Canillas <javierm@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-fbdev@...r.kernel.org,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel.vetter@...ll.ch>,
dri-devel@...ts.freedesktop.org,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Maxime Ripard <maxime@...no.tech>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Emil Velikov <emil.l.velikov@...il.com>
Subject: Re: [PATCH 1/4] drm: Add I2C connector type
Den 02.02.2022 10.14, skrev Thomas Zimmermann:
> Hi Noralf,
>
> since you're here, I'll just hijack the discussion to ask something only
> semi-related.
>
> IIRC the gud driver doesn't update the display immediately during atomic
> commits. Instead, it instructs a helper thread to do the update. What's
> the rational behind this design? Is that something we should adopt for
> other drivers that operate over slow buses (USB, I2C, etc)? Would this
> be relevant for the ssd1307 driver?
>
Async flushing is only necessary on multi display setups where there's
only one rendering loop for all the displays. I saw what tiny/gm12u320.c
did and Hans gave me the rationale. The SPI drivers run flushing inline.
Info on the gud wiki:
https://github.com/notro/gud/wiki/Linux-Host-Driver#asynchronous-flushing
Noralf.
Powered by blists - more mailing lists