diff options
author | Reinhard Nissl <rnissl@gmx.de> | 2012-08-18 08:59:57 -0300 |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2012-09-13 17:42:07 -0300 |
commit | 226143f96fa5ebc0da4a46f8a775129e5b759051 (patch) | |
tree | 7814cef463b17851b6dec1baa4c70204cec2357e /Documentation/DocBook | |
parent | 3c8139477bc55166fa4c125209d193bd9851af3c (diff) | |
download | linux-3.10-226143f96fa5ebc0da4a46f8a775129e5b759051.tar.gz linux-3.10-226143f96fa5ebc0da4a46f8a775129e5b759051.tar.bz2 linux-3.10-226143f96fa5ebc0da4a46f8a775129e5b759051.zip |
[media] stb0899: return internally tuned frequency via get_frontend.
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.
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
...
Signed-off-by: Reinhard Nißl <rnissl@gmx.de>
Cc: Manu Abraham <abraham.manu@gmail.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'Documentation/DocBook')
0 files changed, 0 insertions, 0 deletions