diff options
author | Mauro Carvalho Chehab <mchehab@infradead.org> | 2007-11-15 08:43:53 -0300 |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab@infradead.org> | 2008-01-25 19:02:10 -0200 |
commit | f380e1d2c9a1ff82a89ec68850ce53094359000e (patch) | |
tree | 00813ee13c2420a84bd8d2b98c1934cbaefb0858 /init/calibrate.c | |
parent | 43efe70253dd13b2d22ee51bb474ece25b3b41b1 (diff) |
V4L/DVB (6593): Fix scode table loading
Xceive 2028/3028 has a concept of scode/dcode.
Scode is a table of 16 values (each with 12 bytes i2c sequence).
Dcode is the entry of Scode table that should be used, given a certain
frequency.
The idea is that, depending on what frequency is selected, and according with a
country-based (or standard-based?) table, the Xceive should be "hacked" to
fine-tune that specific frequency.
By default, Scode=0 is used, for undefined frequencies. Also, Scode=0 seems to
be the most used value.
This patch adds the capability of selecting a scode. However, extra work will
be needed to allow auto-selecting the proper scode, for a given set of
frequencies.
I'm not sure what would be the proper way for implementing the dcode selection.
Signed-off-by: Mauro Carvalho Chehab <mchehab@infradead.org>
Diffstat (limited to 'init/calibrate.c')
0 files changed, 0 insertions, 0 deletions