diff options
| author | Bartosz Golaszewski <bgolaszewski@baylibre.com> | 2020-01-10 18:16:41 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2020-02-24 08:36:46 +0100 |
| commit | 989a495ed9a34bc60a33d8ec9ce00dcade40b36c (patch) | |
| tree | 89c5f452081e4ae4554b64b8a18397c4b9f7b30f /include/linux/debugobjects.h | |
| parent | 48be6f9d2f7ef51be716f4c281b878722193c44b (diff) | |
clocksource: davinci: only enable clockevents once tim34 is initialized
[ Upstream commit cea931c25104e6bddc42eb067f58193f355dbdd7 ]
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>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'include/linux/debugobjects.h')
0 files changed, 0 insertions, 0 deletions