| commit | 5252ec9f76aa29c4bb1ab171d5f497c2baeb5657 | |
| author | Michael Krufky <mkrufky@linuxtv.org> | |
| Tue, 12 Dec 2006 05:34:27 +0000 (12 00:34 -0500) | ||
| committer | Chris Wright <chrisw@sous-sol.org> | |
| Sun, 17 Dec 2006 00:20:47 +0000 (16 16:20 -0800) | ||
| tree | 58df724d4c00988fb18aed38840e13bb76e12b01 | treesnapshot (tar.gz zip) |
| parent | 198a9f8d9c6f6260b69e9f68bbc063cecba222b0 | commitdiff |
[PATCH] DVB: lgdt330x: fix signal / lock status detection bug
In some cases when using VSB, the AGC status register has been known to
falsely report "no signal" when in fact there is a carrier lock. The
datasheet labels these status flags as QAM only, yet the lgdt330x
module is using these flags for both QAM and VSB.
This patch allows for the carrier recovery lock status register to be
tested, even if the agc signal status register falsely reports no signal.
Thanks to jcrews from #linuxtv in irc, for initially reporting this bug.
Signed-off-by: Michael Krufky <mkrufky@linuxtv.org>
Signed-off-by: Chris Wright <chrisw@sous-sol.org>
In some cases when using VSB, the AGC status register has been known to
falsely report "no signal" when in fact there is a carrier lock. The
datasheet labels these status flags as QAM only, yet the lgdt330x
module is using these flags for both QAM and VSB.
This patch allows for the carrier recovery lock status register to be
tested, even if the agc signal status register falsely reports no signal.
Thanks to jcrews from #linuxtv in irc, for initially reporting this bug.
Signed-off-by: Michael Krufky <mkrufky@linuxtv.org>
Signed-off-by: Chris Wright <chrisw@sous-sol.org>
| drivers/media/dvb/frontends/lgdt330x.c | diffblobblamehistory |