Il 04/04/2012 15:27, Antti Palosaari ha scritto: > IF frequency is frequency used between tuner and demodulator. Thus it > should be same for the tuner, it is sender Tx, and for demodulator which > receives it. As you can guess it is like radio channel, it will work if > it is a little bit wrong but performance will be reduced. > > IF frequency is generally more tuner characteristic than demodulator. I > mean it is likely tuner decides which is optimal IF for signal tuner is > transferring to demod. Earlier we used configuration option for both > tuner and demod to set IF. But as the fact is tuner must know it always > we added new tuner callback .get_if_frequency() demodulator can ask used > IF from the tuner. > > Recently I converted AF9013 driver to use that .get_if_frequency(). I > think at that point I may have introduced some bug. > > And one point to mention, it is sometimes used a little bit different > IFs that are tuner defaults. It is somehow device design specific, for > maximum performance device engineers will ran some test to find out > optimal IF which gives best performance. One reason could be example > there is RF noise peak (RF spurs) just in used IF which reduces > performance => lets shift default IF a little bit for maximum performance. I found out the origin of the problem: in the old "hacked" driver the demodulator IF frequency was erroneously hard-coded to 4.57 MHz (like with the mxl5007t tuner) so there was a mismatch between the tuner and the demodulator IF setting. In UHF band, the difference was only 0.57 MHz, so it still worked (probably with reduced performance). Instead, in VHF band the difference was over 1 MHz so it was not working. Hacking the tuner IF frequency to 4 MHz in VHF band was enough to get it working, but of course it was not optimal. In the end, there is no bug in the current code. Sorry for all the unnecessary noise about this issue. Regards, Gianluca -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
