From: Antti Palosaari <crope@iki.fi>
To: Hans-Frieder Vogt <hfvogt@gmx.net>
Cc: linux-media@vger.kernel.org, "Michael Büsch" <m@bues.ch>,
"Gianluca Gennari" <gennarone@gmail.com>
Subject: Re: [PATCH v2] af9033: implement ber and ucb functions
Date: Mon, 07 May 2012 16:25:47 +0300 [thread overview]
Message-ID: <4FA7CD5B.3020902@iki.fi> (raw)
In-Reply-To: <201204071634.34179.hfvogt@gmx.net>
On 07.04.2012 17:34, Hans-Frieder Vogt wrote:
> af9033: implement read_ber and read_ucblocks functions. Version 2 of patch that
> reflects my findings on the behaviour of abort_cnt, err_cnt and bit_cnt:
>
> - bit_cnt is always 0x2710 (10000)
> - abort_cnt is between 0 and 0x2710
> - err_cnt is between 0 and 640000 (= 0x2710 * 8 * 8)
>
> in the current implementation BER is calculated as the number of bit errors per
> processed bits, ignoring those bits that are already discarded and counted in
> abort_cnt, i.e. UCBLOCKS.
It still increases UCBLOCKS counter every query even there is no signal
at all. BER is in that case always maximum value. Hymps, maybe I just
apply that still in order to go ahead...
status 00 | signal 0000 | snr 0000 | ber ffffffff | unc 0024b105 |
status 00 | signal 0000 | snr 0000 | ber ffffffff | unc 0024d815 |
One of my plans is to block that kind of "illegal" situations in
frontend core level. As UCB and BER counters are only valid in case of
demod is LOCKed.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2012-05-07 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 14:34 [PATCH v2] af9033: implement ber and ucb functions Hans-Frieder Vogt
2012-05-07 13:25 ` Antti Palosaari [this message]
2012-05-07 18:47 ` 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=4FA7CD5B.3020902@iki.fi \
--to=crope@iki.fi \
--cc=gennarone@gmail.com \
--cc=hfvogt@gmx.net \
--cc=linux-media@vger.kernel.org \
--cc=m@bues.ch \
/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).