diff options
| author | Daniel Vetter | 2014-09-15 14:55:29 +0200 |
|---|---|---|
| committer | Daniel Vetter | 2014-09-19 14:43:21 +0200 |
| commit | 133217869ea7f328acedab2ed2ec1ad41b6390bd (patch) | |
| tree | c08d9e3182fcbb332b68a286fa5987e75dda6163 /drivers/gpu/drm/i915/intel_display.c | |
| parent | drm/i915: Clarify irq_lock locking, irq handlers (diff) | |
| download | kernel-qcow2-linux-133217869ea7f328acedab2ed2ec1ad41b6390bd.tar.gz kernel-qcow2-linux-133217869ea7f328acedab2ed2ec1ad41b6390bd.tar.xz kernel-qcow2-linux-133217869ea7f328acedab2ed2ec1ad41b6390bd.zip | |
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>
Diffstat (limited to 'drivers/gpu/drm/i915/intel_display.c')
0 files changed, 0 insertions, 0 deletions