Anyone may call clk_round_rate() with a zero rate value, so we have to
protect against that.
Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx>
Acked-by: Wolfram Sang <wsa+renesas@xxxxxxxxxxxxxxxxxxxx>
I agree that this should not be fixed in the core because the fixup is
really driver dependant.
Dunno, zero frequency seems generally insane to me.
It is useful to find the lowest frequency a clock can support. Basically
it is a search for the floor frequency.
Why not just use 1? Or are you assuming that some hardware could actually
support 0 Hz?
Replying to myself: yes, this has happened to me, when I forgot to override
the EXTAL frequency in the board .dts file (default was 0).
So it was a good thing that the driver crashed, it let you find a bug ;-)