Re: [PATCH] clk-si544: Properly round requested frequency to nearest match

2018-06-02 Thread Stephen Boyd
Quoting Mike Looijmans (2018-05-31 07:03:55) > The si544 driver had a rounding problem that using the result of > clk_round_rate > may set the clock to yet another rate, for example: > clk_round_rate(19500) = 19499 > clk_round_rate(19499) = 19498 > > Clients would expect that

Re: [PATCH] clk-si544: Properly round requested frequency to nearest match

2018-06-02 Thread Stephen Boyd
Quoting Mike Looijmans (2018-05-31 07:03:55) > The si544 driver had a rounding problem that using the result of > clk_round_rate > may set the clock to yet another rate, for example: > clk_round_rate(19500) = 19499 > clk_round_rate(19499) = 19498 > > Clients would expect that

Re: [PATCH] clk-si544: Properly round requested frequency to nearest match

2018-06-01 Thread Mike Looijmans
On 31-05-18 17:34, Stephen Boyd wrote: Quoting Mike Looijmans (2018-05-31 07:03:55) The si544 driver had a rounding problem that using the result of clk_round_rate may set the clock to yet another rate, for example: clk_round_rate(19500) = 19499 clk_round_rate(19499) = 19498

Re: [PATCH] clk-si544: Properly round requested frequency to nearest match

2018-06-01 Thread Mike Looijmans
On 31-05-18 17:34, Stephen Boyd wrote: Quoting Mike Looijmans (2018-05-31 07:03:55) The si544 driver had a rounding problem that using the result of clk_round_rate may set the clock to yet another rate, for example: clk_round_rate(19500) = 19499 clk_round_rate(19499) = 19498

Re: [PATCH] clk-si544: Properly round requested frequency to nearest match

2018-05-31 Thread Stephen Boyd
Quoting Mike Looijmans (2018-05-31 07:03:55) > The si544 driver had a rounding problem that using the result of > clk_round_rate > may set the clock to yet another rate, for example: > clk_round_rate(19500) = 19499 > clk_round_rate(19499) = 19498 > > Clients would expect that

Re: [PATCH] clk-si544: Properly round requested frequency to nearest match

2018-05-31 Thread Stephen Boyd
Quoting Mike Looijmans (2018-05-31 07:03:55) > The si544 driver had a rounding problem that using the result of > clk_round_rate > may set the clock to yet another rate, for example: > clk_round_rate(19500) = 19499 > clk_round_rate(19499) = 19498 > > Clients would expect that

[PATCH] clk-si544: Properly round requested frequency to nearest match

2018-05-31 Thread Mike Looijmans
The si544 driver had a rounding problem that using the result of clk_round_rate may set the clock to yet another rate, for example: clk_round_rate(19500) = 19499 clk_round_rate(19499) = 19498 Clients would expect that after clk_set_rate(clk, freq2=clk_round_rate(clk, freq)) the

[PATCH] clk-si544: Properly round requested frequency to nearest match

2018-05-31 Thread Mike Looijmans
The si544 driver had a rounding problem that using the result of clk_round_rate may set the clock to yet another rate, for example: clk_round_rate(19500) = 19499 clk_round_rate(19499) = 19498 Clients would expect that after clk_set_rate(clk, freq2=clk_round_rate(clk, freq)) the