drm/amd/display: LFC not working on 2.0x range monitors (v2)
authorAric Cyr <aric.cyr@amd.com>
Wed, 11 Mar 2020 22:10:20 +0000 (18:10 -0400)
committerAlex Deucher <alexander.deucher@amd.com>
Tue, 31 Mar 2020 16:26:14 +0000 (12:26 -0400)
commit5a6b5458699d8e6fdb5ae09d950935a48b79f8c7
tree996af433eda1fcea30567e111aaada10c1824e4a
parent5c41c023f8b213d425af973a4dd83f5b9bc0bfb2
drm/amd/display: LFC not working on 2.0x range monitors (v2)

[Why]
Nominal pixel clock and EDID information differ in precision so although
monitor reports maximum refresh is 2x minimum, LFC was not being
enabled.

[How]
Use minimum refresh rate as nominal/2 when EDID dictates that min
refresh = max refresh/2.

v2: squash in 64 bit divide fix

Signed-off-by: Aric Cyr <aric.cyr@amd.com>
Reviewed-by: Nicholas Kazlauskas <Nicholas.Kazlauskas@amd.com>
Acked-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drivers/gpu/drm/amd/display/modules/freesync/freesync.c