summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/display/dc/inc/hw/stream_encoder.h
diff options
context:
space:
mode:
authorNikola Cornij <nikola.cornij@amd.com>2019-10-16 14:34:15 -0400
committerAlex Deucher <alexander.deucher@amd.com>2019-11-13 15:29:43 -0500
commita5132f9728dc7c310736b83422e93e0ad563a3b6 (patch)
tree9eb9272363b577cd4b33d802859a00051e08983e /drivers/gpu/drm/amd/display/dc/inc/hw/stream_encoder.h
parent4338ffa8df23d6665f53dd38da2e415940e3bf13 (diff)
downloadlinux-stable-a5132f9728dc7c310736b83422e93e0ad563a3b6.tar.gz
linux-stable-a5132f9728dc7c310736b83422e93e0ad563a3b6.tar.bz2
linux-stable-a5132f9728dc7c310736b83422e93e0ad563a3b6.zip
drm/amd/display: Add a sanity check for DSC already enabled/disabled
[why] If acquire/release DSC resource sequence is affected by a regression, it can happen that the already-in-use DSC HW block is being wrongly re-used for a different pipe. The reverse is also possible, i.e. already-disabled DSC HW block could be disabled from other context. [how] Read back the enable state of DSC HW and report an error if duplicate enable or disable was attempted. Signed-off-by: Nikola Cornij <nikola.cornij@amd.com> Reviewed-by: Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com> Acked-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/amd/display/dc/inc/hw/stream_encoder.h')
0 files changed, 0 insertions, 0 deletions