All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <m.chehab@samsung.com>
To: Luis Alves <ljalvs@gmail.com>
Cc: linux-media@vger.kernel.org, crope@iki.fi
Subject: Re: [PATCH] si2157: Fix DVB-C bandwidth.
Date: Tue, 22 Jul 2014 13:10:59 -0300	[thread overview]
Message-ID: <20140722131059.4ad26777.m.chehab@samsung.com> (raw)
In-Reply-To: <1406027388-10336-1-git-send-email-ljalvs@gmail.com>

Em Tue, 22 Jul 2014 12:09:48 +0100
Luis Alves <ljalvs@gmail.com> escreveu:

> This patch fixes DVB-C reception.
> Without setting the bandwidth to 8MHz the received stream gets corrupted.
> 
> Regards,
> Luis
> 
> Signed-off-by: Luis Alves <ljalvs@gmail.com>
> ---
>  drivers/media/tuners/si2157.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/media/tuners/si2157.c b/drivers/media/tuners/si2157.c
> index 6c53edb..e2de428 100644
> --- a/drivers/media/tuners/si2157.c
> +++ b/drivers/media/tuners/si2157.c
> @@ -245,6 +245,7 @@ static int si2157_set_params(struct dvb_frontend *fe)
>  			break;
>  	case SYS_DVBC_ANNEX_A:
>  			delivery_system = 0x30;
> +			bandwidth = 0x08;

Hmm... this patch looks wrong, as it will break DVB-C support where
the bandwidth is lower than 6MHz.

The DVB core sets c->bandwidth_hz for DVB-C based on the rolloff and
the symbol rate. If this is not working for you, then something else
is likely wrong.

I suggest you to add a printk() there to show what's the value set
at c->bandwidth_hz and what's the symbol rate that you're using.

On DVB-C, the rolloff is fixed (1.15 for annex A and 1.13 for Annex C).
Not sure if DVB-C2 allows selecting a different rolloff factor, nor
if si2157 works with DVB-C2.

>  			break;
>  	default:
>  			ret = -EINVAL;

  parent reply	other threads:[~2014-07-22 16:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 11:09 [PATCH] si2157: Fix DVB-C bandwidth Luis Alves
2014-07-22 15:59 ` Matthias Schwarzott
2014-07-22 16:10 ` Mauro Carvalho Chehab [this message]
2014-07-22 16:28   ` Luis Alves
2014-07-22 17:03     ` Mauro Carvalho Chehab
2014-07-22 19:12       ` Antti Palosaari

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=20140722131059.4ad26777.m.chehab@samsung.com \
    --to=m.chehab@samsung.com \
    --cc=crope@iki.fi \
    --cc=linux-media@vger.kernel.org \
    --cc=ljalvs@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.