target/linux/brcm2708/patches-4.14/950-0190-drm-vc4-Don-t-wait-for-vblank-on-fkms-cursor-updates.patch

   1 From 2c77eedbc7d668d128af3bec2633d55e01c9e67c Mon Sep 17 00:00:00 2001
   2 From: Eric Anholt <eric@anholt.net>
   3 Date: Mon, 5 Feb 2018 18:53:18 +0000
   4 Subject: [PATCH 190/454] drm/vc4: Don't wait for vblank on fkms cursor
   5  updates.
   6
   7 We don't use the same async update path between fkms and normal kms,
   8 and the normal kms workaround ended up making us wait.  This became a
   9 larger problem in rpi-4.14.y, as the USB HID update rate throttling
  10 got (accidentally?) dropped.
  11
  12 Signed-off-by: Eric Anholt <eric@anholt.net>
  13 ---
  14  drivers/gpu/drm/vc4/vc4_kms.c | 3 ++-
  15  1 file changed, 2 insertions(+), 1 deletion(-)
  16
  17 --- a/drivers/gpu/drm/vc4/vc4_kms.c
  18 +++ b/drivers/gpu/drm/vc4/vc4_kms.c
  19 @@ -53,7 +53,8 @@ vc4_atomic_complete_commit(struct drm_at
  20          * display lists before we free it and potentially reallocate
  21          * and overwrite the dlist memory with a new modeset.
  22          */
  23 -       state->legacy_cursor_update = false;
  24 +       if (!vc4->firmware_kms)
  25 +               state->legacy_cursor_update = false;
  26
  27         drm_atomic_helper_commit_hw_done(state);
  28