[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGb2v65RJ2iwTr1bxXxXAROLtg2a1KP2x36uXpjGs=r38NrM6g@mail.gmail.com>
Date: Thu, 24 Jan 2019 16:56:53 +0800
From: Chen-Yu Tsai <wens@...e.org>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Maxime Ripard <maxime.ripard@...tlin.com>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] clocksource: sun5i: fail gracefully when clock rate is unavailable
On Thu, Jan 10, 2019 at 5:19 PM Daniel Lezcano
<daniel.lezcano@...aro.org> wrote:
>
> On 10/01/2019 07:22, Chen-Yu Tsai wrote:
> > If the clock tree is not fully populated when the timer-sun5i init code
> > is called, attempts to get the clock rate for the timer would fail and
> > return 0.
> >
> > Make the init code for both clock events and clocksource check the
> > returned clock rate and fail gracefully if the result is 0, instead of
> > causing a divide by 0 exception later on.
> >
> > Fixes: 4a59058f0b09 ("clocksource/drivers/sun5i: Refactor the current code")
> > Signed-off-by: Chen-Yu Tsai <wens@...e.org>
> > ---
>
> Applied thanks.
I'm not seeing this in linux-next, nor the patch
arm64: arch_timer: Workaround for Allwinner A64 timer instability
Any idea where these ended up?
Thanks
ChenYu
Powered by blists - more mailing lists