mirror of
https://github.com/hardkernel/linux.git
synced 2026-04-16 18:40:44 +09:00
There are some rates that would be ranged for better clock jitter at Chrome OS tree, like 25.175Mhz would range to 25.170732Mhz. But due to the clock is aglined to KHz in struct drm_display_mode, this would bring some inaccurate error if we still run the compute_n math, so let's just code an const table for it until we can actually get the right clock rate. Change-Id: Ief14b7c9bffa95ff3b173925f3e1bd795625320d Signed-off-by: Yakir Yang <ykk@rock-chips.com> Reviewed-on: https://chromium-review.googlesource.com/316280 Commit-Ready: Douglas Anderson <dianders@chromium.org> Tested-by: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org>