Re: [PATCH] [dvbv5-scan] wait no more than timeout when scanning

2016-07-25 Thread Abylay Ospan
Hi Mauro, I have sent two patches to ML. One is for dvbv5-scan (v3 of this patch) and second for lgdt3306a driver. Now I have achieved 4 minutes for full scan (file us-ATSC-center-frequencies-8VSB with 68 frequencies inside). This is much better than 2 hours before :) But need to test this

Re: [PATCH] [dvbv5-scan] wait no more than timeout when scanning

2016-07-24 Thread Abylay Ospan
Hi Mauro, I have checked 'do_timeout' - it's bit different that we want. I just updated patch to use 'clock_gettime(CLOCK_MONOTONIC' to avoid timestamps 'rollup'. Hope it's ok. The problem is really annoying because scanning takes a lot of time. Without this patch command 'dvbv5-scan

[PATCH] [dvbv5-scan] wait no more than timeout when scanning

2016-07-24 Thread Abylay Ospan
some frontends (mentioned on lgdt3306a) wait timeout inside code like: for (i = 20; i > 0; i--) { msleep(50); If there is no-LOCK then dvbv5-scan spent a lot of time (doing 40x calls). This patch introduce timeout which 4 sec * multiply. So we do not wait more than 4 sec (or so) if no-LOCK.

Re: [PATCH] [dvbv5-scan] wait no more than timeout when scanning

2016-07-22 Thread Mauro Carvalho Chehab
Hi Abylay, Em Fri, 22 Jul 2016 13:54:37 -0400 Abylay Ospan escreveu: > some frontends (mentioned on lgdt3306a) wait timeout inside code like: > for (i = 20; i > 0; i--) { > msleep(50); > > If there is no-LOCK then dvbv5-scan spent a lot of time (doing 40x calls). > This

[PATCH] [dvbv5-scan] wait no more than timeout when scanning

2016-07-22 Thread Abylay Ospan
some frontends (mentioned on lgdt3306a) wait timeout inside code like: for (i = 20; i > 0; i--) { msleep(50); If there is no-LOCK then dvbv5-scan spent a lot of time (doing 40x calls). This patch introduce timeout which 4 sec * multiply. So we do not wait more than 4 sec (or so) if no-LOCK.