clocksource/drivers/tegra: Cycles can't be 0
authorDmitry Osipenko <digetx@gmail.com>
Tue, 18 Jun 2019 14:03:57 +0000 (17:03 +0300)
committerDaniel Lezcano <daniel.lezcano@linaro.org>
Tue, 25 Jun 2019 17:49:18 +0000 (19:49 +0200)
commit0ef6b01d024c24fad307b277cfa4a2be7d25dc29
tree05aab71c90a634168a29b9b45cc04b9b8bb2b93c
parentfc9babc2574691d3bbf0428f007b22261fed55c6
clocksource/drivers/tegra: Cycles can't be 0

Tegra's timer uses n+1 scheme for the counter, i.e. timer will fire after
one tick if 0 is loaded. The minimum and maximum numbers of oneshot ticks
are defined by clockevents_config_and_register(min, max) invocation and
the min value is set to 1 tick. Hence "cycles" value can't ever be 0,
unless it's a bug in clocksource core.

Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
Acked-by: Jon Hunter <jonathanh@nvidia.com>
Acked-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
drivers/clocksource/timer-tegra.c