On Mon, Nov 13, 2017 at 3:27 PM, Brian Starkey <[email protected]> wrote: > clk_round_rate() is intended to be used to round a given clock rate to > the closest one achievable by the actual clock. This implies that the > input to clk_round_rate() is expected to be unachievable - and such > cases shouldn't be treated as exceptional. > > To reflect this, remove the WARN_ONs which trigger when an unachievable > clock rate is passed to vexpress_osc_round_rate(). > > Reported-by: Vladimir Murzin <[email protected]> > Signed-off-by: Brian Starkey <[email protected]> > Acked-by: Sudeep Holla <[email protected]>
Ping!
