Re: [PATCH v1 2/5] clk: Introduce clk_round_rate_unboundly()

2020-05-27 Thread Stephen Boyd
Quoting Dmitry Osipenko (2020-05-27 10:57:01) > 27.05.2020 08:55, Stephen Boyd \u043f\u0438\u0448\u0435\u0442: > > Quoting Dmitry Osipenko (2020-03-30 16:16:14) > >> In same cases it may be desired to round clock's rate without taking into > >> account current min/max requests made by the clock's u

Re: [PATCH v1 2/5] clk: Introduce clk_round_rate_unboundly()

2020-05-27 Thread Dmitry Osipenko
27.05.2020 08:55, Stephen Boyd пишет: > Quoting Dmitry Osipenko (2020-03-30 16:16:14) >> In same cases it may be desired to round clock's rate without taking into >> account current min/max requests made by the clock's users. One example is >> building up OPP table based on a possible clock rates.

Re: [PATCH v1 2/5] clk: Introduce clk_round_rate_unboundly()

2020-05-26 Thread Stephen Boyd
Quoting Dmitry Osipenko (2020-03-30 16:16:14) > In same cases it may be desired to round clock's rate without taking into > account current min/max requests made by the clock's users. One example is > building up OPP table based on a possible clock rates. > > Signed-off-by: Dmitry Osipenko > ---

Re: [PATCH v1 2/5] clk: Introduce clk_round_rate_unboundly()

2020-05-26 Thread Stephen Boyd
Quoting Dmitry Osipenko (2020-03-30 16:16:14) > In same cases it may be desired to round clock's rate without taking into > account current min/max requests made by the clock's users. One example is > building up OPP table based on a possible clock rates. Shouldn't the OPP table come from firmware