diff options
| author | David Herrmann <dh.herrmann@gmail.com> | 2014-01-23 15:14:56 +0100 |
|---|---|---|
| committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2014-03-07 15:30:49 +0200 |
| commit | 60231da1275fbd46a0977219a95d42c53a5c91ff (patch) | |
| tree | 7db73541850bcb0bdbccec28552867937866e4e2 /drivers/md | |
| parent | 65b4021ed67622b675b431fc2f3633b2af8cea6d (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>
Diffstat (limited to 'drivers/md')
0 files changed, 0 insertions, 0 deletions