[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <54D4A18D.3010504@cogentembedded.com>
Date: Fri, 06 Feb 2015 14:12:13 +0300
From: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>
CC: Mike Turquette <mturquette@...aro.org>,
Wolfram Sang <wsa@...-dreams.de>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Stephen Boyd <sboyd@...eaurora.org>,
Ulrich Hecht <ulrich.hecht+renesas@...il.com>,
Wolfram Sang <wsa@...g-engineering.com>,
linux-sh@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] clk: shmobile: div6: Avoid division by zero in .round_rate()
Hello.
On 2/5/2015 8:19 PM, Laurent Pinchart wrote:
>>>>>>> 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@...der.be>
>>>>>> Acked-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
>>>>>> 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 ;-)
None of the clock drivers crashed, but the SDHI driver hanged instead, and
I spent much time tracing it in order to find where it hanged. :-/
WBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists