drm/i915: Nuke debug messages from the pipe update critical section
authorVille Syrjälä <ville.syrjala@linux.intel.com>
Tue, 7 Mar 2017 20:54:19 +0000 (22:54 +0200)
committerVille Syrjälä <ville.syrjala@linux.intel.com>
Wed, 8 Mar 2017 11:02:17 +0000 (13:02 +0200)
commitc3f8ad57a01a31397e5a0349a226a32f35ddc19c
treec4103d2fca2fd9a4590dd910fb5872f1a74327fc
parent7ffe939dd9c71e149f31817394b70b52b4067304
drm/i915: Nuke debug messages from the pipe update critical section

printks are slow so we should not be doing them from the vblank evade
critical section. These could explain why we sometimes seem to
blow past our 100 usec deadline.

The problem has been there ever since commit bfd16b2a23dc ("drm/i915:
Make updating pipe without modeset atomic.") but it may not have
been readily visible until commit e1edbd44e23b ("drm/i915: Complain
if we take too long under vblank evasion.") increased our chances
of noticing it.

Cc: stable@vger.kernel.org
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Fixes: bfd16b2a23dc ("drm/i915: Make updating pipe without modeset atomic.")
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20170307205419.19447-1-ville.syrjala@linux.intel.com
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
drivers/gpu/drm/i915/intel_display.c