linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gianluca Gennari <gennarone@gmail.com>
To: Antti Palosaari <crope@iki.fi>
Cc: linux-media@vger.kernel.org, m@bues.ch, hfvogt@gmx.net,
	mchehab@redhat.com
Subject: Re: [PATCH 3/5] tda18218: fix IF frequency for 7MHz bandwidth channels
Date: Fri, 06 Apr 2012 12:40:10 +0200	[thread overview]
Message-ID: <4F7EC80A.4010906@gmail.com> (raw)
In-Reply-To: <4F7C4C3D.1090702@iki.fi>

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

  reply	other threads:[~2012-04-06 10:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 21:25 [PATCH 0/5] af9035: support for tda18218 tuner, new USB IDs and more Gianluca Gennari
2012-04-02 21:25 ` [PATCH 1/5] af9035: add USB id for 07ca:a867 Gianluca Gennari
2012-04-02 22:32   ` Antti Palosaari
2012-04-02 21:25 ` [PATCH 2/5] af9035: add support for the tda18218 tuner Gianluca Gennari
2012-04-02 22:33   ` Antti Palosaari
2012-04-02 21:25 ` [PATCH 3/5] tda18218: fix IF frequency for 7MHz bandwidth channels Gianluca Gennari
2012-04-02 22:40   ` Antti Palosaari
2012-04-03  0:44     ` Gianluca Gennari
2012-04-03  7:18       ` poma
2012-04-03 10:19       ` Antti Palosaari
2012-04-03 16:03         ` Gianluca Gennari
2012-04-04 13:15         ` Gianluca Gennari
2012-04-04 13:27           ` Antti Palosaari
2012-04-06 10:40             ` Gianluca Gennari [this message]
2012-04-02 21:25 ` [PATCH 4/5] af9035: fix warning Gianluca Gennari
2012-04-02 22:41   ` Antti Palosaari
2012-04-02 21:25 ` [PATCH 5/5] af9035: use module_usb_driver macro Gianluca Gennari
2012-04-02 22:42   ` Antti Palosaari
2012-04-06 20:19 ` Re : [PATCH 0/5] af9035: support for tda18218 tuner, new USB IDs and more Sril

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=4F7EC80A.4010906@gmail.com \
    --to=gennarone@gmail.com \
    --cc=crope@iki.fi \
    --cc=hfvogt@gmx.net \
    --cc=linux-media@vger.kernel.org \
    --cc=m@bues.ch \
    --cc=mchehab@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).