summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/Kconfig
diff options
context:
space:
mode:
authorNoralf Trønnes2016-04-28 17:18:33 +0200
committerDaniel Vetter2016-05-02 16:22:03 +0200
commiteaa434defaca1781fb2932c685289b610aeb8b4b (patch)
tree718167fd30355f4366b6224320044d35f19da92c /drivers/gpu/drm/Kconfig
parentdrm/qxl: Change drm_fb_helper_sys_*() calls to sys_*() (diff)
downloadkernel-qcow2-linux-eaa434defaca1781fb2932c685289b610aeb8b4b.tar.gz
kernel-qcow2-linux-eaa434defaca1781fb2932c685289b610aeb8b4b.tar.xz
kernel-qcow2-linux-eaa434defaca1781fb2932c685289b610aeb8b4b.zip
drm/fb-helper: Add fb_deferred_io support
This adds deferred io support to drm_fb_helper. The fbdev framebuffer changes are flushed using the callback (struct drm_framebuffer *)->funcs->dirty() by a dedicated worker ensuring that it always runs in process context. For those wondering why we need to be able to handle atomic calling contexts: Both panic paths and cursor code and fbcon blanking can run from atomic. See commit bcb39af4486be07e896fc374a2336bad3104ae0a Author: Dave Airlie <airlied@redhat.com> Date: Thu Feb 7 11:19:15 2013 +1000 drm/udl: make usage as a console safer for where this was originally discovered. Signed-off-by: Noralf Trønnes <noralf@tronnes.org> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> [danvet: Augment commit message with why we need to handle atomic contexts.] Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Link: http://patchwork.freedesktop.org/patch/msgid/1461856717-6476-4-git-send-email-noralf@tronnes.org
Diffstat (limited to 'drivers/gpu/drm/Kconfig')
-rw-r--r--drivers/gpu/drm/Kconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
index f2a74d0b68ae..414c79bf63a7 100644
--- a/drivers/gpu/drm/Kconfig
+++ b/drivers/gpu/drm/Kconfig
@@ -52,6 +52,7 @@ config DRM_KMS_FB_HELPER
select FB_CFB_FILLRECT
select FB_CFB_COPYAREA
select FB_CFB_IMAGEBLIT
+ select FB_DEFERRED_IO
help
FBDEV helpers for KMS drivers.