Messages in this thread | | | From | Bartosz Golaszewski <> | Date | Fri, 10 Jan 2020 18:05:14 +0100 | Subject | Re: [PATCH v2 1/3] clocksource: davinci: only enable tim34 in periodic mode once it's initialized |
| |
pt., 10 sty 2020 o 00:12 Daniel Lezcano <daniel.lezcano@linaro.org> napisał(a): > > On 24/12/2019 11:03, Bartosz Golaszewski wrote: > > From: Bartosz Golaszewski <bgolaszewski@baylibre.com> > > > > The DM365 platform has a strange quirk (only present when using ancient > > u-boot - mainline u-boot v2013.01 and later works fine) where if we > > enable the second half of the timer in periodic mode before we do its > > initialization - the time won't start flowing and we can't boot. > > > > When using more recent u-boot, we can enable the timer, then reinitialize > > it and all works fine. > > > > I've been unable to figure out why that is, but a workaround for this > > is straightforward - don't enable the tim34 timer in periodic mode until > > it's properly initialized. > > > > Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com> > > Why not move clockevents_config_and_register() after > davinci_clocksource_init_tim34() is called ?
Ha! Yes, that works too. I'll send a v3 shortly.
Bart
| |