drm/amd/display: Use VUPDATE_NO_LOCK instead of VUPDATE for dcn30
authorNicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Wed, 8 Jul 2020 17:29:58 +0000 (13:29 -0400)
committerAlex Deucher <alexander.deucher@amd.com>
Fri, 10 Jul 2020 21:41:12 +0000 (17:41 -0400)
commitc74f9322484869c10117eb068998250df3714486
treef3bb2aa7f094a192e731a263a4784e4a27c1df0c
parent131a3c7474adce63b988f6913085aee8c6e7c313
drm/amd/display: Use VUPDATE_NO_LOCK instead of VUPDATE for dcn30

[Why]
Soft hangs occur when FreeSync is engaged since we utilize VUPDATE
(which doesn't fire when holding the pipe lock) to send back vblank
events when FreeSync is active.

[How]
The alternative (working) interrupt source for this mechanism is
VUPDATE_NO_LOCK. We already use this all other DCN revisions so align
dcn30 with those as well.

Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Reviewed-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drivers/gpu/drm/amd/display/dc/irq/dcn30/irq_service_dcn30.c