aboutsummaryrefslogtreecommitdiffstats
path: root/common/recipes-kernel/linux/linux-yocto-4.19.8/0115-drm-amd-display-Add-back-code-to-allow-for-rounding-.patch
diff options
context:
space:
mode:
Diffstat (limited to 'common/recipes-kernel/linux/linux-yocto-4.19.8/0115-drm-amd-display-Add-back-code-to-allow-for-rounding-.patch')
-rw-r--r--common/recipes-kernel/linux/linux-yocto-4.19.8/0115-drm-amd-display-Add-back-code-to-allow-for-rounding-.patch48
1 files changed, 48 insertions, 0 deletions
diff --git a/common/recipes-kernel/linux/linux-yocto-4.19.8/0115-drm-amd-display-Add-back-code-to-allow-for-rounding-.patch b/common/recipes-kernel/linux/linux-yocto-4.19.8/0115-drm-amd-display-Add-back-code-to-allow-for-rounding-.patch
new file mode 100644
index 00000000..6e9c206a
--- /dev/null
+++ b/common/recipes-kernel/linux/linux-yocto-4.19.8/0115-drm-amd-display-Add-back-code-to-allow-for-rounding-.patch
@@ -0,0 +1,48 @@
+From e7ddb135fdb5b62cc424ee46fd5202d58cd38bdd Mon Sep 17 00:00:00 2001
+From: Anthony Koo <Anthony.Koo@amd.com>
+Date: Thu, 5 Apr 2018 15:20:15 -0400
+Subject: [PATCH 0115/2940] drm/amd/display: Add back code to allow for
+ rounding error
+
+Signed-off-by: Anthony Koo <Anthony.Koo@amd.com>
+Reviewed-by: Aric Cyr <Aric.Cyr@amd.com>
+Acked-by: Harry Wentland <harry.wentland@amd.com>
+Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
+---
+ .../gpu/drm/amd/display/modules/freesync/freesync.c | 13 ++++++++++++-
+ 1 file changed, 12 insertions(+), 1 deletion(-)
+
+diff --git a/drivers/gpu/drm/amd/display/modules/freesync/freesync.c b/drivers/gpu/drm/amd/display/modules/freesync/freesync.c
+index 4887c888bbe7..abd5c9374eb3 100644
+--- a/drivers/gpu/drm/amd/display/modules/freesync/freesync.c
++++ b/drivers/gpu/drm/amd/display/modules/freesync/freesync.c
+@@ -896,6 +896,17 @@ bool mod_freesync_is_valid_range(struct mod_freesync *mod_freesync,
+ unsigned long long nominal_field_rate_in_uhz =
+ mod_freesync_calc_nominal_field_rate(stream);
+
++ /* Allow for some rounding error of actual video timing by taking ceil.
++ * For example, 144 Hz mode timing may actually be 143.xxx Hz when
++ * calculated from pixel rate and vertical/horizontal totals, but
++ * this should be allowed instead of blocking FreeSync.
++ */
++ nominal_field_rate_in_uhz = div_u64(nominal_field_rate_in_uhz, 1000000);
++ min_refresh_cap_in_uhz /= 1000000;
++ max_refresh_cap_in_uhz /= 1000000;
++ min_refresh_request_in_uhz /= 1000000;
++ max_refresh_request_in_uhz /= 1000000;
++
+ // Check nominal is within range
+ if (nominal_field_rate_in_uhz > max_refresh_cap_in_uhz ||
+ nominal_field_rate_in_uhz < min_refresh_cap_in_uhz)
+@@ -921,7 +932,7 @@ bool mod_freesync_is_valid_range(struct mod_freesync *mod_freesync,
+
+ // For variable range, check for at least 10 Hz range
+ if ((max_refresh_request_in_uhz != min_refresh_request_in_uhz) &&
+- (max_refresh_request_in_uhz - min_refresh_request_in_uhz < 10000000))
++ (max_refresh_request_in_uhz - min_refresh_request_in_uhz < 10))
+ return false;
+
+ return true;
+--
+2.17.1
+