summaryrefslogtreecommitdiffstats
path: root/include/drm/drm_mm.h
diff options
context:
space:
mode:
authorDaniel Vetter <daniel.vetter@ffwll.ch>2012-12-17 12:13:23 +0100
committerDaniel Vetter <daniel.vetter@ffwll.ch>2013-01-20 22:17:17 +0100
commit20c60c35de3285222b3476c3445c66bedf0c449c (patch)
tree96993a1477448059651019185c34460d6ea7a245 /include/drm/drm_mm.h
parent5d7a951537927555fa1286a338e1b91c3b8b7445 (diff)
downloadlinux-20c60c35de3285222b3476c3445c66bedf0c449c.tar.bz2
drm/fb_helper: check whether fbcon is bound
We need to make sure that the fbcon is still bound when touching the hw, since otherwise we might corrupt the modeset state of kms clients. X mostly works around that with VT switching and setting the VT into raw mode, which disables most fbcon events. Raw kms test programs though don't do that dance, and in the future we might want to aim to abolish CONFIG_VT anyway. So improve preventive measures a bit. To do so, extract the existing logic for handling hotplug events (which X can't block with the current set of tricks) and reuse it for the fbdev blanking helper. Long-term we really need to either scrap this all and only have a OOPS console, or come up with a saner model for device ownership sharing between fbdev/fbcon and kms userspace. Reviewed-by: Rob Clark <rob@ti.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'include/drm/drm_mm.h')
0 files changed, 0 insertions, 0 deletions