diff options
| author | Thomas Hellstrom <thellstrom@vmware.com> | 2018-05-23 16:14:54 +0200 |
|---|---|---|
| committer | Thomas Hellstrom <thellstrom@vmware.com> | 2018-05-23 16:52:55 +0200 |
| commit | 6a93cea15ed38e2dba4a0552483d28b7a87a03bd (patch) | |
| tree | 7b9b63367aa8a37d097ebff652b7ed01f5e0697e /drivers/gpu/drm/drm_gem_cma_helper.c | |
| parent | f37230c0ad481091bc136788ff8b37dc86300c6d (diff) | |
drm/vmwgfx: Schedule an fb dirty update after resume
We have had problems displaying fbdev after a resume and as a
workaround we have had to call vmw_fb_refresh(). This has had
a number of unwanted side-effects. The root of the problem was,
however that the coalesced fbdev dirty region was not empty on
the first dirty_mark() after a resume, so a flush was never
scheduled.
Fix this by force scheduling an fbdev flush after resume, and
remove the workaround.
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
Reviewed-by: Brian Paul <brianp@vmware.com>
Reviewed-by: Deepak Rawat <drawat@vmware.com>
Diffstat (limited to 'drivers/gpu/drm/drm_gem_cma_helper.c')
0 files changed, 0 insertions, 0 deletions