Re: [PATCH v8 4/6] clocksource: stm32: only use 32 bits timers

2017-12-08 Thread Benjamin Gaignard
2017-12-08 10:29 GMT+01:00 Daniel Lezcano : > On 08/12/2017 10:25, Benjamin Gaignard wrote: >> 2017-12-08 9:34 GMT+01:00 Daniel Lezcano : >>> On 14/11/2017 09:52, Benjamin Gaignard wrote: The clock driving counters is at 90MHz so the maximum period for 16 bis counters is around 750 ms >>>

Re: [PATCH v8 4/6] clocksource: stm32: only use 32 bits timers

2017-12-08 Thread Daniel Lezcano
On 08/12/2017 10:25, Benjamin Gaignard wrote: > 2017-12-08 9:34 GMT+01:00 Daniel Lezcano : >> On 14/11/2017 09:52, Benjamin Gaignard wrote: >>> The clock driving counters is at 90MHz so the maximum period >>> for 16 bis counters is around 750 ms >> >> 728 us >> >>> which is a short period for a clo

Re: [PATCH v8 4/6] clocksource: stm32: only use 32 bits timers

2017-12-08 Thread Benjamin Gaignard
2017-12-08 9:34 GMT+01:00 Daniel Lezcano : > On 14/11/2017 09:52, Benjamin Gaignard wrote: >> The clock driving counters is at 90MHz so the maximum period >> for 16 bis counters is around 750 ms > > 728 us > >> which is a short period for a clocksource. > > Which clocksource are you talking about ?

Re: [PATCH v8 4/6] clocksource: stm32: only use 32 bits timers

2017-12-08 Thread Daniel Lezcano
On 14/11/2017 09:52, Benjamin Gaignard wrote: > The clock driving counters is at 90MHz so the maximum period > for 16 bis counters is around 750 ms 728 us > which is a short period for a clocksource. Which clocksource are you talking about ? > For 32 bits counters this period is close > 47 seco

Re: [PATCH v8 4/6] clocksource: stm32: only use 32 bits timers

2017-12-07 Thread Daniel Lezcano
On 07/12/2017 21:36, Benjamin Gaignard wrote: > 2017-12-07 17:49 GMT+01:00 Daniel Lezcano : >> On 07/12/2017 17:33, Benjamin Gaignard wrote: >>> 2017-12-07 16:27 GMT+01:00 Daniel Lezcano : On 14/11/2017 09:52, Benjamin Gaignard wrote: > The clock driving counters is at 90MHz so the maximum

Re: [PATCH v8 4/6] clocksource: stm32: only use 32 bits timers

2017-12-07 Thread Benjamin Gaignard
2017-12-07 17:49 GMT+01:00 Daniel Lezcano : > On 07/12/2017 17:33, Benjamin Gaignard wrote: >> 2017-12-07 16:27 GMT+01:00 Daniel Lezcano : >>> On 14/11/2017 09:52, Benjamin Gaignard wrote: The clock driving counters is at 90MHz so the maximum period for 16 bis counters is around 750 ms wh

Re: [PATCH v8 4/6] clocksource: stm32: only use 32 bits timers

2017-12-07 Thread Daniel Lezcano
On 07/12/2017 17:33, Benjamin Gaignard wrote: > 2017-12-07 16:27 GMT+01:00 Daniel Lezcano : >> On 14/11/2017 09:52, Benjamin Gaignard wrote: >>> The clock driving counters is at 90MHz so the maximum period >>> for 16 bis counters is around 750 ms which is a short period >>> for a clocksource. >> >>

Re: [PATCH v8 4/6] clocksource: stm32: only use 32 bits timers

2017-12-07 Thread Benjamin Gaignard
2017-12-07 16:27 GMT+01:00 Daniel Lezcano : > On 14/11/2017 09:52, Benjamin Gaignard wrote: >> The clock driving counters is at 90MHz so the maximum period >> for 16 bis counters is around 750 ms which is a short period >> for a clocksource. > > Isn't it 728us ? yes it is: 2^16 / 90.000.000 => 728

Re: [PATCH v8 4/6] clocksource: stm32: only use 32 bits timers

2017-12-07 Thread Daniel Lezcano
On 14/11/2017 09:52, Benjamin Gaignard wrote: > The clock driving counters is at 90MHz so the maximum period > for 16 bis counters is around 750 ms which is a short period > for a clocksource. Isn't it 728us ? > For 32 bits counters this period is close > 47 secondes which is more acceptable. >

[PATCH v8 4/6] clocksource: stm32: only use 32 bits timers

2017-11-14 Thread Benjamin Gaignard
The clock driving counters is at 90MHz so the maximum period for 16 bis counters is around 750 ms which is a short period for a clocksource. For 32 bits counters this period is close 47 secondes which is more acceptable. This patch remove 16 bits counters support and makes sure that they won't be