All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Reinhard Nissl <rnissl@gmx.de>
Cc: Manu Abraham <abraham.manu@gmail.com>, linux-media@vger.kernel.org
Subject: Re: STV0299: reading property DTV_FREQUENCY -- what am I expected to get?
Date: Wed, 15 Aug 2012 19:10:27 -0300	[thread overview]
Message-ID: <502C1E53.4090103@redhat.com> (raw)
In-Reply-To: <502AB1D2.3070209@gmx.de>

Em 14-08-2012 17:15, Reinhard Nissl escreveu:
> Hi,
> 
> Am 14.08.2012 14:05, schrieb Manu Abraham:
> 
>>> My other device, a STB0899, always reports the set frequency. So it seems
>>> driver dependent whether it reports the actually locked frequency found by
>>> the zig-zag-algorithm or just the set frequency to tune to.
>>
>> The STV0299 blindly sets the value based on a software zigzag (due to simpler
>> hardware), but this might not be accurate enough. On the other hand, the
>> STB0899 internally does zig-zag in hardware for DVB-S2, and partly in
>> software for DVB-S.
>>
>> In any event, the get_frontend callback should return the value that is read
>> from the demodulator registers, rather than the cached original value that
>> which was requested to be tuned.
>>
>> The stb0899 returns only the cached value IIRC. Maybe I will fix this soon,
>> or maybe you can send a patch.
> 
> See the attached patch.
> 
> This is what I get after the patch:
> 
> Sat.    Pol.    Band    Freq (MHz) Set    Freq (MHz) Get    Delta (MHz)
> S19,2E    H    L    10744    10748,474    4,474
> S19,2E    H    L    10773    10777,944    4,944
> S19,2E    H    L    10832    10836,953    4,953
> S19,2E    H    L    10861    10868,774    7,774
> S19,2E    H    L    10920    10924,312    4,312
> S19,2E    H    L    11023    11026,827    3,827
> S19,2E    H    L    11170    11175,423    5,423
> S19,2E    H    L    11243    11248,452    5,452
> S19,2E    H    L    11302    11307,371    5,371
> S19,2E    H    L    11361    11366,427    5,427
> S19,2E    H    L    11420    11425,473    5,473
> S19,2E    H    L    11464    11468,876    4,876
> S19,2E    H    L    11493    11498,421    5,421
> S19,2E    H    L    11523    11529,080    6,080
> S19,2E    H    L    11582    11586,942    4,942
> S19,2E    H    L    11611    11618,785    7,785
> S19,2E    H    L    11641    11645,951    4,951
> S19,2E    H    L    11670    11675,450    5,450
> S19,2E    H    H    11719    11724,970    5,970
> S19,2E    H    H    11758    11763,975    5,975
> S19,2E    H    H    11797    11802,978    5,978
> S19,2E    H    H    11836    11841,972    5,972
> S19,2E    H    H    11875    11880,951    5,951
> 
> I'll have to let VDR "travel" across the transponders several times to see whether I get similar results for the previously mentioned transponder on the stv0299 device.
> 
> Bye.

The patch seems to be working. Anyway, for it to be merged, you'll
need to be sending it together with your SOB (Signed-off-by),
and using the -p1 format e. g. something like:

--- a/drivers/media/dvb/frontends/stb0899_drv.c	2012-08-14 21:59:59.000000000 +0200
+++ b/drivers/media/dvb/frontends/stb0899_drv.c	2012-08-14 21:29:17.000000000 +0200

as otherwise developer's scripts won't get it right.

Thanks,
Mauro.

  parent reply	other threads:[~2012-08-15 22:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14  8:53 STV0299: reading property DTV_FREQUENCY -- what am I expected to get? Reinhard Nissl
2012-08-14 11:10 ` Antti Palosaari
2012-08-14 12:05 ` Manu Abraham
2012-08-14 20:15   ` Reinhard Nissl
2012-08-15 14:41     ` Reinhard Nissl
2012-08-15 22:10     ` Mauro Carvalho Chehab [this message]
2012-08-18 12:59       ` Reinhard Nissl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=502C1E53.4090103@redhat.com \
    --to=mchehab@redhat.com \
    --cc=abraham.manu@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=rnissl@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.