drm/atmel-hlcdc: allow selecting a higher pixel-clock than requested
authorPeter Rosin <peda@axentia.se>
Fri, 24 Aug 2018 09:24:58 +0000 (11:24 +0200)
committerBoris Brezillon <boris.brezillon@bootlin.com>
Mon, 27 Aug 2018 19:13:01 +0000 (21:13 +0200)
commit9946a3a9dbedaaacef8b7e94f6ac144f1daaf1de
treee6a61224906265e8cf0e782423b16578111ed138
parent319711f982084b044d3dac6ae58e3d801ae4ca43
drm/atmel-hlcdc: allow selecting a higher pixel-clock than requested

But only if the highest pixel-clock frequency lower than requested
is significantly less accurate than the lowest frequency higher than
requested.

I pulled "10 times" as the discriminator out of the hat, and went with
that.

This is useful, if e.g. the target pixel-clock is 65MHz and the sys_clk
is 132MHz. In this case the highest possible pixel-clock lower than the
requested 65MHz is 52.8MHz, which is almost 20% off (and outside the
spec for the panel). The lowest possible pixel-clock higher than 65MHz
is 66MHz, which is a *much* better match, and only 1.5% off.

Signed-off-by: Peter Rosin <peda@axentia.se>
Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180824092458.13165-3-peda@axentia.se
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c