diff --git a/Documentation/DocBook/media/dvb/frontend.xml b/Documentation/DocBook/media/dvb/frontend.xml
index bcee1d9fc73db11a2462cbd65cf22e1d1e06a8ef..16a4648043d6c2325866f5753c823d4fe649c33a 100644
--- a/Documentation/DocBook/media/dvb/frontend.xml
+++ b/Documentation/DocBook/media/dvb/frontend.xml
@@ -29,19 +29,29 @@
specification is available at
Eutelsat.
-
Querying frontend information
-Information about the frontend can be queried with
- FE_GET_INFO.
+Usually, the first thing to do when the frontend is opened is to
+ check the frontend capabilities. This is done using FE_GET_INFO. This ioctl will enumerate
+ the DVB API version and other characteristics about the frontend, and
+ can be opened either in read only or read/write mode.
-Querying frontend status
+Querying frontend status and statistics
-Information about the frontend tuner locking status can be queried with
- FE_READ_STATUS.
+Once FE_SET_PROPERTY
+ is called, the frontend will run a kernel thread that will periodically
+ check for the tuner lock status and provide statistics about the quality
+ of the signal.
+The information about the frontend tuner locking status can be queried
+ using FE_READ_STATUS.
+Signal statistics are provided via FE_GET_PROPERTY.
+ Please notice that several statistics require the demodulator to be fully
+ locked (e. g. with FE_HAS_LOCK bit set). See
+ Frontend statistics indicators
+ for more details.
&sub-dvbproperty;