Lyude Paul a7e3ad5fdc drm/vblank: Use spin_(un)lock_irq() in drm_crtc_vblank_off()
This got me confused for a bit while looking over this code: I had been
planning on adding some blocking function calls into this function, but
seeing the irqsave/irqrestore variants of spin_(un)lock() didn't make it
very clear whether or not that would actually be safe.

So I went ahead and reviewed every single driver in the kernel that uses
this function, and they all fall into three categories:

* Driver probe code
* ->atomic_disable() callbacks
* Legacy modesetting callbacks

All of these will be guaranteed to have IRQs enabled, which means it's
perfectly safe to block here. Just to make things a little less
confusing to others in the future, let's switch over to
spin_lock_irq()/spin_unlock_irq() to make that fact a little more
obvious.

Signed-off-by: Lyude Paul <lyude@redhat.com>
Reviewed-by: Daniel Vetter <daniel@ffwll.ch>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Acked-by: Dave Airlie <airlied@gmail.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20200627194657.156514-3-lyude@redhat.com
2020-07-16 18:16:31 -04:00
..
2020-06-13 13:04:36 -07:00
2020-06-19 13:09:40 -07:00
2020-06-09 10:04:47 -07:00
2020-06-19 13:11:26 -07:00
2020-06-07 10:59:32 -07:00
2020-06-13 13:29:16 -07:00
2020-06-07 10:59:32 -07:00
2020-06-03 15:00:05 -07:00
2020-06-13 13:29:16 -07:00
2020-06-04 11:03:45 -07:00
2020-06-02 15:29:19 -07:00
2020-06-13 13:29:16 -07:00
2020-07-01 10:49:02 +02:00
2020-06-13 13:29:16 -07:00
2020-06-11 12:53:23 -07:00
2020-06-13 13:29:16 -07:00
2020-06-13 13:29:16 -07:00
2020-06-04 19:09:28 +02:00
2020-06-08 13:01:08 -07:00
2020-06-08 13:01:08 -07:00
2020-06-07 16:11:23 -07:00
2020-06-07 10:59:32 -07:00
2020-06-13 13:29:16 -07:00
2020-06-13 13:29:16 -07:00
2020-06-13 13:29:16 -07:00
2020-06-13 13:29:16 -07:00