From: Antti Palosaari <crope@iki.fi>
To: Malcolm Priestley <tvboxspy@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 6/7] af9013 Stop OFSM while channel changing.
Date: Sat, 12 Nov 2011 18:39:39 +0200 [thread overview]
Message-ID: <4EBEA14B.6070504@iki.fi> (raw)
In-Reply-To: <4ebe9717.5b6be30a.26ea.ffff9ad7@mx.google.com>
On 11/12/2011 05:56 PM, Malcolm Priestley wrote:
> To minimise corruptions on channel change.
>
> Signed-off-by: Malcolm Priestley<tvboxspy@gmail.com>
> ---
> drivers/media/dvb/frontends/af9013.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/media/dvb/frontends/af9013.c b/drivers/media/dvb/frontends/af9013.c
> index 38a6ea2..6a5b40c 100644
> --- a/drivers/media/dvb/frontends/af9013.c
> +++ b/drivers/media/dvb/frontends/af9013.c
> @@ -629,6 +629,10 @@ static int af9013_set_frontend(struct dvb_frontend *fe,
> params->u.ofdm.bandwidth);
>
> state->frequency = params->frequency;
> + /* Stop OFSM */
> + ret = af9013_write_reg(state, 0xffff, 1);
> + if (ret)
> + goto error;
>
> /* program tuner */
> if (mutex_lock_interruptible(state->fe_mutex)< 0)
That seems to be simple.
That means there is no corruptions for the other frontend after that? It
sounds rather weird that setting one registers to other demod helps the
other demod. Generally programming one demod should not be any effect to
other demods having the same board.
Or do you mean it block corruptions on demod in question?
Corruptions in channel change sounds something like normal.
regards
Antti
--
http://palosaari.fi/
prev parent reply other threads:[~2011-11-12 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 15:56 [PATCH 6/7] af9013 Stop OFSM while channel changing Malcolm Priestley
2011-11-12 16:39 ` Antti Palosaari [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=4EBEA14B.6070504@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=tvboxspy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox