drm/omap: fix suspend/resume handling

Browse source

For legacy reasons omapdss handles system suspend/resume via PM notifier
callback, where the driver disables/resumes all the outputs.

This doesn't work well with omapdrm. What happens on suspend is that the
omapdss disables the displays while omapdrm is still happily continuing
its work, possibly waiting for an vsync irq, which will never come if
the display output is disabled, leading to timeouts and errors sent to
userspace.

This patch moves the suspend/resume handling to omapdrm, and the
suspend/resume is now done safely inside modeset lock.

Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>

...

This commit is contained in:

Tomi Valkeinen 2015-10-02 11:10:42 +03:00

parent bfeece5533

commit 92bf0f9e2a

4 changed files with 44 additions and 67 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

29

drivers/gpu/drm/omapdrm/dss/core.c

View file

36

drivers/gpu/drm/omapdrm/dss/display.c

View file

2

drivers/gpu/drm/omapdrm/dss/dss.h

View file

44

drivers/gpu/drm/omapdrm/omap_drv.c

View file