Recently added FE_NONE to the enum fe_status, so update the
documentation accordingly.
[mchehab@s-opensource.com: change description to actually
reflect what FE_NONE means: no lock of any kind]
Signed-off-by: Colin Ian King <colin.king@canonical.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
- .. row 2
+ - .. _FE-NONE:
+
+ ``FE_NONE``
+
+ - The frontend doesn't have any kind of lock. That's the initial frontend status
+
+ - .. row 3
+
- .. _FE-HAS-SIGNAL:
``FE_HAS_SIGNAL``
- The frontend has found something above the noise level
- - .. row 3
+ - .. row 4
- .. _FE-HAS-CARRIER:
- The frontend has found a DVB signal
- - .. row 4
+ - .. row 5
- .. _FE-HAS-VITERBI:
- The frontend FEC inner coding (Viterbi, LDPC or other inner code)
is stable
- - .. row 5
+ - .. row 6
- .. _FE-HAS-SYNC:
- Synchronization bytes was found
- - .. row 6
+ - .. row 7
- .. _FE-HAS-LOCK:
- The DVB were locked and everything is working
- - .. row 7
+ - .. row 8
- .. _FE-TIMEDOUT:
- no lock within the last about 2 seconds
- - .. row 8
+ - .. row 9
- .. _FE-REINIT: