summaryrefslogtreecommitdiffstats
path: root/drivers/clk/ti
diff options
context:
space:
mode:
authorTomi Valkeinen <tomi.valkeinen@ti.com>2014-02-13 12:03:59 +0200
committerMike Turquette <mturquette@linaro.org>2014-02-26 18:23:46 -0800
commitb11d282dbea27db1788893115dfca8a7856bf205 (patch)
tree445a271a85312da38b01072699437cf05217252c /drivers/clk/ti
parent1887c3a64fab8300a5be3fb5fd8d6474a63b50a0 (diff)
downloadop-kernel-dev-b11d282dbea27db1788893115dfca8a7856bf205.zip
op-kernel-dev-b11d282dbea27db1788893115dfca8a7856bf205.tar.gz
clk: divider: fix rate calculation for fractional rates
clk-divider.c does not calculate the rates consistently at the moment. As an example, on OMAP3 we have a clock divider with a source clock of 864000000 Hz. With dividers 6, 7 and 8 the theoretical rates are: 6: 144000000 7: 123428571.428571... 8: 108000000 Calling clk_round_rate() with the rate in the first column will give the rate in the second column: 144000000 -> 144000000 143999999 -> 123428571 123428572 -> 123428571 123428571 -> 108000000 Note how clk_round_rate() returns 123428571 for rates from 123428572 to 143999999, which is mathematically correct, but when clk_round_rate() is called with 123428571, the returned value is surprisingly 108000000. This means that the following code works a bit oddly: rate = clk_round_rate(clk, 123428572); clk_set_rate(clk, rate); As clk_set_rate() also does clock rate rounding, the result is that the clock is set to the rate of 108000000, not 123428571 returned by the clk_round_rate. This patch changes the clk-divider.c to use DIV_ROUND_UP when calculating the rate. This gives the following behavior which fixes the inconsistency: 144000000 -> 144000000 143999999 -> 123428572 123428572 -> 123428572 123428571 -> 108000000 Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com> Signed-off-by: Mike Turquette <mturquette@linaro.org>
Diffstat (limited to 'drivers/clk/ti')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud