Re: [PATCH 8/8] LinuxPPS: pps_gen_parport: Add check for bad clocksource.

2017-03-04 Thread Rodolfo Giometti
On 03/04/17 10:19, Alexander Gerasiov wrote: Hello Rodolfo, I should say, that I found this solution is not the best. For example on high speed PCs (I think over 3GHz) 5 iteration is not enough and module stops working after several hours. That makes it not user-friendly, cause user had to calib

Re: [PATCH 8/8] LinuxPPS: pps_gen_parport: Add check for bad clocksource.

2017-03-04 Thread Alexander Gerasiov
Hello Rodolfo, I should say, that I found this solution is not the best. For example on high speed PCs (I think over 3GHz) 5 iteration is not enough and module stops working after several hours. That makes it not user-friendly, cause user had to calibrate and set failure_iterations manually. It w

Re: [PATCH 8/8] LinuxPPS: pps_gen_parport: Add check for bad clocksource.

2017-03-04 Thread Rodolfo Giometti
On 02/15/17 15:31, Andrey Drobyshev wrote: From: Nikita Edward Baruzdin This commit is supposed to resolve the issue with hard lockups on systems using jiffies as their clock source. Namely, it sets limits on number of iterations clock source may remain unchanged (i. e. not being updated for on

[PATCH 8/8] LinuxPPS: pps_gen_parport: Add check for bad clocksource.

2017-02-15 Thread Andrey Drobyshev
From: Nikita Edward Baruzdin This commit is supposed to resolve the issue with hard lockups on systems using jiffies as their clock source. Namely, it sets limits on number of iterations clock source may remain unchanged (i. e. not being updated for one reason or another, as it is with jiffies cl