tree c08d9e3182fcbb332b68a286fa5987e75dda6163
parent 222c7f51b074cc8bfbda5821ee7f875e51f841b5
author Daniel Vetter <daniel.vetter@ffwll.ch> 1410785729 +0200
committer Daniel Vetter <daniel.vetter@ffwll.ch> 1411130601 +0200

drm/i915: Clarify irq_lock locking, special cases

Grab bag for all the special cases:
- i9xx_check_fifo_underruns is only called from crtc_enable hooks,
  i.e. process context.
- i915_enable_asle_pipestat is only called from interrupt postinstall
  hooks. So again process context.
- gen8_irq_power_well_post_enable is called from the runtime pm code,
  which again means process context.
- The open-coded hpd_irq_setup loop in _thaw is also running in process
  context.

So for all of them the plain _irq variant is sufficient.

Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>