From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Michael Krufky <mkrufky@kernellabs.com>,
Devin Heitmueller <dheitmueller@kernellabs.com>,
Tim Gardner <tim.gardner@canonical.com>,
linux-media@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [media] tuners/xc5000: fix MODE_AIR in xc5000_set_params()
Date: Tue, 5 Feb 2013 21:00:34 -0200 [thread overview]
Message-ID: <20130205210034.59034ed2@redhat.com> (raw)
In-Reply-To: <20130113193133.GA5907@elgon.mountain>
Em Sun, 13 Jan 2013 22:31:33 +0300
Dan Carpenter <dan.carpenter@oracle.com> escreveu:
> There is a missing break so we use XC_RF_MODE_CABLE instead of
> XC_RF_MODE_AIR.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
> Static checker stuff. Untested.
>
> diff --git a/drivers/media/tuners/xc5000.c b/drivers/media/tuners/xc5000.c
> index dc93cf3..d6be1b6 100644
> --- a/drivers/media/tuners/xc5000.c
> +++ b/drivers/media/tuners/xc5000.c
> @@ -785,6 +785,7 @@ static int xc5000_set_params(struct dvb_frontend *fe)
> return -EINVAL;
> }
> priv->rf_mode = XC_RF_MODE_AIR;
> + break;
There one small change with this patch. On this part of the code:
static int xc_SetSignalSource(struct xc5000_priv *priv, u16 rf_mode)
{
dprintk(1, "%s(%d) Source = %s\n", __func__, rf_mode,
rf_mode == XC_RF_MODE_AIR ? "ANTENNA" : "CABLE");
if ((rf_mode != XC_RF_MODE_AIR) && (rf_mode != XC_RF_MODE_CABLE)) {
rf_mode = XC_RF_MODE_CABLE;
printk(KERN_ERR
"%s(), Invalid mode, defaulting to CABLE",
__func__);
}
return xc_write_reg(priv, XREG_SIGNALSOURCE, rf_mode);
}
It will set the value for XREG_SIGNALSOURCE with a different value.
While I didn't test it, such change makes sense, by looking at xc5000
"open source" datasheet.
So, it looks correct on my eyes.
While the datasheet doesn't give any glue, my guess is that changing from
"cable" to "air" will just optimize the tuner's sensibility for either
air (where signals can be weaker) or cable, so I bet that the effects of
a change like that won't be easily noticed.
I'll apply it, in order to give people some chance to test it.
Cheers,
Mauro
prev parent reply other threads:[~2013-02-05 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 19:31 [media] tuners/xc5000: fix MODE_AIR in xc5000_set_params() Dan Carpenter
2013-02-05 23:00 ` Mauro Carvalho Chehab [this message]
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=20130205210034.59034ed2@redhat.com \
--to=mchehab@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=dheitmueller@kernellabs.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mkrufky@kernellabs.com \
--cc=tim.gardner@canonical.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).