diff options
| author | Bartosz Golaszewski <bgolaszewski@baylibre.com> | 2020-01-10 18:16:41 +0100 |
|---|---|---|
| committer | Sekhar Nori <nsekhar@ti.com> | 2020-01-13 13:20:00 +0530 |
| commit | cea931c25104e6bddc42eb067f58193f355dbdd7 (patch) | |
| tree | 13c058839243191937dc5b922cfbad0fee4b258a /sound/soc/Makefile | |
| parent | e42617b825f8073569da76dc4510bfa019b1c35a (diff) | |
clocksource: davinci: only enable clockevents once tim34 is initialized
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>
Signed-off-by: Sekhar Nori <nsekhar@ti.com>
Diffstat (limited to 'sound/soc/Makefile')
0 files changed, 0 insertions, 0 deletions