| commit | 2f14c0c8cae8e9e3b603a3f91909baba66540027 | [log] [tgz] |
|---|---|---|
| author | Mario Limonciello <mario.limonciello@amd.com> | Tue Mar 05 14:34:24 2024 -0600 |
| committer | Alex Deucher <alexander.deucher@amd.com> | Wed Mar 20 13:12:56 2024 -0400 |
| tree | 838811cb7f28e9a9f3a367ddc553ba504c6599a5 | |
| parent | 119b225f01e4d3ce974cd3b4d982c76a380c796d [diff] |
drm/amd/display: Use freesync when `DRM_EDID_FEATURE_CONTINUOUS_FREQ` found The monitor shipped with the Framework 16 supports VRR [1], but it's not being advertised. This is because the detailed timing block doesn't contain `EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max frequencies. This check however is superfluous for this case because update_display_info() calls drm_get_monitor_range() to get these ranges already. So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then turn on freesync without extra checks. v2: squash in fix from Harry Closes: https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/ Closes: https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/ Closes: https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338 Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf Signed-off-by: Mario Limonciello <mario.limonciello@amd.com> Reviewed-by: Harry Wentland <harry.wentland@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>