Messages in this thread | | | From | Bartosz Golaszewski <> | Date | Sat, 11 Jan 2020 11:19:58 +0100 | Subject | Re: [PATCH v3 1/3] clocksource: davinci: only enable clockevents once tim34 is initialized |
| |
pt., 10 sty 2020 o 18:56 Daniel Lezcano <daniel.lezcano@linaro.org> napisał(a): > > On 10/01/2020 18:16, 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. > > > > To work around this issue only enable clockevents once tim34 is > > initialized i.e. move clockevents_config_and_register() below tim34 > > initialization. > > > > Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com> > > Shall I take it through my tree? >
Not sure, I'd say Sekhar should take it through arm-soc together with the latter two patches if he's ok with this. Let's wait for him to respond.
Bart
| |