summaryrefslogtreecommitdiff
path: root/linux/drivers/media/video/tuner-i2c.h
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@infradead.org>2007-11-15 09:43:53 -0200
committerMauro Carvalho Chehab <mchehab@infradead.org>2007-11-15 09:43:53 -0200
commit3e03a8f07af8cf0f94f93ec445689e7e8813b038 (patch)
treecb186cf9ab9c333ea8f6021e3e78187dc0bc424d /linux/drivers/media/video/tuner-i2c.h
parentd59bcff278a29b7c11e9821630c7f75fabb5287e (diff)
downloadmediapointer-dvb-s2-3e03a8f07af8cf0f94f93ec445689e7e8813b038.tar.gz
mediapointer-dvb-s2-3e03a8f07af8cf0f94f93ec445689e7e8813b038.tar.bz2
Fix scode table loading
From: Mauro Carvalho Chehab <mchehab@infradead.org> 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 'linux/drivers/media/video/tuner-i2c.h')
0 files changed, 0 insertions, 0 deletions