Re: [PATCH 1/2] rtc: ds1374: wdt: Fix issue with timeout scaling from secs to wdt ticks

2017-05-04 Thread Alexandre Belloni
On 24/04/2017 at 15:05:11 -0700, Moritz Fischer wrote: > Fix commit 920f91e50c5b ("drivers/rtc/rtc-ds1374.c: add watchdog support") > > The issue is that the internal counter that triggers the watchdog reset > is actually running at 4096 Hz instead of 1Hz, therefore the value > given by userland

Re: [PATCH 1/2] rtc: ds1374: wdt: Fix issue with timeout scaling from secs to wdt ticks

2017-05-04 Thread Alexandre Belloni
On 24/04/2017 at 15:05:11 -0700, Moritz Fischer wrote: > Fix commit 920f91e50c5b ("drivers/rtc/rtc-ds1374.c: add watchdog support") > > The issue is that the internal counter that triggers the watchdog reset > is actually running at 4096 Hz instead of 1Hz, therefore the value > given by userland

[PATCH 1/2] rtc: ds1374: wdt: Fix issue with timeout scaling from secs to wdt ticks

2017-04-24 Thread Moritz Fischer
Fix commit 920f91e50c5b ("drivers/rtc/rtc-ds1374.c: add watchdog support") The issue is that the internal counter that triggers the watchdog reset is actually running at 4096 Hz instead of 1Hz, therefore the value given by userland (in sec) needs to be multiplied by 4096 to get the correct

[PATCH 1/2] rtc: ds1374: wdt: Fix issue with timeout scaling from secs to wdt ticks

2017-04-24 Thread Moritz Fischer
Fix commit 920f91e50c5b ("drivers/rtc/rtc-ds1374.c: add watchdog support") The issue is that the internal counter that triggers the watchdog reset is actually running at 4096 Hz instead of 1Hz, therefore the value given by userland (in sec) needs to be multiplied by 4096 to get the correct