drm/nouveau: Don't enabling polling twice on runtime resume
authorLyude Paul <lyude@redhat.com>
Thu, 12 Jan 2017 02:25:23 +0000 (21:25 -0500)
committerDave Airlie <airlied@redhat.com>
Fri, 27 Jan 2017 00:43:42 +0000 (10:43 +1000)
commitcae9ff036eea577856d5b12860b4c79c5e71db4a
treef230de52d5ed8f7a47580615006d3729ced8825d
parent6c971c09f38704513c426ba6515f22fb3d6c87d5
drm/nouveau: Don't enabling polling twice on runtime resume

As it turns out, on cards that actually have CRTCs on them we're already
calling drm_kms_helper_poll_enable(drm_dev) from
nouveau_display_resume() before we call it in
nouveau_pmops_runtime_resume(). This leads us to accidentally trying to
enable polling twice, which results in a potential deadlock between the
RPM locks and drm_dev->mode_config.mutex if we end up trying to enable
polling the second time while output_poll_execute is running and holding
the mode_config lock. As such, make sure we only enable polling in
nouveau_pmops_runtime_resume() if we need to.

This fixes hangs observed on the ThinkPad W541

Signed-off-by: Lyude <lyude@redhat.com>
Cc: Hans de Goede <hdegoede@redhat.com>
Cc: Kilian Singer <kilian.singer@quantumtechnology.info>
Cc: Lukas Wunner <lukas@wunner.de>
Cc: David Airlie <airlied@redhat.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
drivers/gpu/drm/nouveau/nouveau_display.c
drivers/gpu/drm/nouveau/nouveau_drm.c