Lines Matching refs:statistics

108       :ref:`DVBv5 statistics <dvbv5_stats>` via ``.read_status``.
109       Yet, there are a number of callbacks meant to get statistics for
164 Digital TV Frontend statistics
171 :ref:`statistics <frontend-stat-properties>` meant to help tuning the device
174 For each statistics measurement, the driver should set the type of scale used,
175 or ``FE_SCALE_NOT_AVAILABLE`` if the statistics is not available on a given
176 time. Drivers should also provide the number of statistics for each type.
188 And, when the statistics got updated, set the scale::
193 .. [#f2] For ISDB-T, it may provide both a global statistics and a per-layer
194    set of statistics. On such cases, len should be equal to 4. The first
205 Groups of statistics  argument
208 There are several groups of statistics currently supported:
219     typically, this statistics is always available [#f3]_.
221   - Drivers should try to make it available all the times, as this statistics
249   - Due to its nature, those statistics depend on full coding lock
258   - Not all frontends provide this kind of statistics.
260   - Due to its nature, those statistics depend on inner coding lock (e. g.
268   - Due to its nature, those statistics depend on full coding lock
275 A typical example of the logic that handle status and statistics is::
342 Driver should check such bit before making the statistics available.
379 If the driver doesn't provide a statistics available check bit
389 On such drivers, a typical routine to get statistics would be like
432 Please notice that, on both cases, we're getting the statistics using the