Re: [PATCH v3 7/8] clocksource/drivers/tegra: Cycles can't be 0

2019-06-20 Thread Dmitry Osipenko
19.06.2019 11:19, Thierry Reding пишет: > On Tue, Jun 18, 2019 at 05:03:57PM +0300, Dmitry Osipenko wrote: >> 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_a

Re: [PATCH v3 7/8] clocksource/drivers/tegra: Cycles can't be 0

2019-06-19 Thread Thierry Reding
On Tue, Jun 18, 2019 at 05:03:57PM +0300, Dmitry Osipenko wrote: > 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 mi

Re: [PATCH v3 7/8] clocksource/drivers/tegra: Cycles can't be 0

2019-06-18 Thread Jon Hunter
On 18/06/2019 15:03, Dmitry Osipenko wrote: > 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

[PATCH v3 7/8] clocksource/drivers/tegra: Cycles can't be 0

2019-06-18 Thread Dmitry Osipenko
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