projects / GitHub / LineageOS / android_kernel_motorola_exynos9610.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 65b4021) | patch
fbdev: vesafb: add dev->remove() callback
authorDavid Herrmann <dh.herrmann@gmail.com>
Thu, 23 Jan 2014 14:14:56 +0000 (15:14 +0100)
committerTomi Valkeinen <tomi.valkeinen@ti.com>
Fri, 7 Mar 2014 13:30:49 +0000 (15:30 +0200)
commit60231da1275fbd46a0977219a95d42c53a5c91ff
tree7db73541850bcb0bdbccec28552867937866e4e2tree | snapshot (tar.gz zip)
parent65b4021ed67622b675b431fc2f3633b2af8cea6dcommit | diff
fbdev: vesafb: add dev->remove() callback

If x86-sysfb platform-devices are removed from a system, we should
properly unload vesafb. Otherwise, we end up releasing the parent while
our vesa framebuffer is still running. This currently works just fine, but
will cause problems on handover to real hw. So add the ->remove() callback
and unregister vesafb.

Signed-off-by: David Herrmann <dh.herrmann@gmail.com>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
drivers/video/vesafb.c diff | blob | blame | history