aboutsummaryrefslogtreecommitdiffstats
path: root/common/recipes-kernel/linux/linux-yocto-4.14.71/0027-drm-amd-display-Block-3D-Timings.patch
diff options
context:
space:
mode:
Diffstat (limited to 'common/recipes-kernel/linux/linux-yocto-4.14.71/0027-drm-amd-display-Block-3D-Timings.patch')
-rw-r--r--common/recipes-kernel/linux/linux-yocto-4.14.71/0027-drm-amd-display-Block-3D-Timings.patch38
1 files changed, 38 insertions, 0 deletions
diff --git a/common/recipes-kernel/linux/linux-yocto-4.14.71/0027-drm-amd-display-Block-3D-Timings.patch b/common/recipes-kernel/linux/linux-yocto-4.14.71/0027-drm-amd-display-Block-3D-Timings.patch
new file mode 100644
index 00000000..f444fbec
--- /dev/null
+++ b/common/recipes-kernel/linux/linux-yocto-4.14.71/0027-drm-amd-display-Block-3D-Timings.patch
@@ -0,0 +1,38 @@
+From b24d0a2fa8e2b9cbbcbf84cad50c892c209ed6e0 Mon Sep 17 00:00:00 2001
+From: Joshua Aberback <Joshua.Aberback@amd.com>
+Date: Tue, 29 Nov 2016 17:56:05 -0500
+Subject: [PATCH 0027/4131] drm/amd/display: Block 3D Timings
+
+- we don't yet support 3D timings in DAL3
+- somehow a code path was being executed that resulted in HW programming
+for a 3D timing, which caused 3D displays to show half the desktop in one
+frame, and the other half of the desktop in the next frame
+- blocking all 3D timings in timing generator validation until we
+implement proper 3D timing support
+
+Signed-off-by: Joshua Aberback <Joshua.Aberback@amd.com>
+Reviewed-by: Tony Cheng <Tony.Cheng@amd.com>
+Acked-by: Harry Wentland <Harry.Wentland@amd.com>
+Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
+---
+ drivers/gpu/drm/amd/display/dc/dce110/dce110_timing_generator.c | 4 ++++
+ 1 file changed, 4 insertions(+)
+
+diff --git a/drivers/gpu/drm/amd/display/dc/dce110/dce110_timing_generator.c b/drivers/gpu/drm/amd/display/dc/dce110/dce110_timing_generator.c
+index b1c9712..12a2587 100644
+--- a/drivers/gpu/drm/amd/display/dc/dce110/dce110_timing_generator.c
++++ b/drivers/gpu/drm/amd/display/dc/dce110/dce110_timing_generator.c
+@@ -1113,6 +1113,10 @@ bool dce110_timing_generator_validate_timing(
+ if (!timing)
+ return false;
+
++ /* Currently we don't support 3D, so block all 3D timings */
++ if (timing->timing_3d_format != TIMING_3D_FORMAT_NONE)
++ return false;
++
+ /* Check maximum number of pixels supported by Timing Generator
+ * (Currently will never fail, in order to fail needs display which
+ * needs more than 8192 horizontal and
+--
+2.7.4
+