Re: [v2,5/6] drm/fb-helper: Schedule deferred-I/O worker after writing to framebuffer

On 17.11.2022 18:21, Marek Szyprowski wrote: > On 17.11.2022 17:07, Thomas Zimmermann wrote: >> Am 17.11.22 um 13:57 schrieb Marek Szyprowski: >>> On 15.11.2022 12:58, Thomas Zimmermann wrote: Schedule the deferred-I/O worker instead of the damage worker after writing to the fbdev

Re: [v2,5/6] drm/fb-helper: Schedule deferred-I/O worker after writing to framebuffer

On 17.11.2022 17:07, Thomas Zimmermann wrote: > Am 17.11.22 um 13:57 schrieb Marek Szyprowski: >> On 15.11.2022 12:58, Thomas Zimmermann wrote: >>> Schedule the deferred-I/O worker instead of the damage worker after >>> writing to the fbdev framebuffer. The deferred-I/O worker then performs >>>

Re: [v2,5/6] drm/fb-helper: Schedule deferred-I/O worker after writing to framebuffer

Hi Am 17.11.22 um 13:57 schrieb Marek Szyprowski: Hi Thomas, On 15.11.2022 12:58, Thomas Zimmermann wrote: Schedule the deferred-I/O worker instead of the damage worker after writing to the fbdev framebuffer. The deferred-I/O worker then performs the dirty-fb update. The fbdev emulation will

Re: [v2,5/6] drm/fb-helper: Schedule deferred-I/O worker after writing to framebuffer

Hi Thomas, On 15.11.2022 12:58, Thomas Zimmermann wrote: > Schedule the deferred-I/O worker instead of the damage worker after > writing to the fbdev framebuffer. The deferred-I/O worker then performs > the dirty-fb update. The fbdev emulation will initialize deferred I/O > for all drivers that