Lines Matching refs:statistics
110 :ref:`DVBv5 statistics <dvbv5_stats>` via ``.read_status``.
111 Yet, there are a number of callbacks meant to get statistics for
166 Digital TV Frontend statistics
173 :ref:`statistics <frontend-stat-properties>` meant to help tuning the device
176 For each statistics measurement, the driver should set the type of scale used,
177 or ``FE_SCALE_NOT_AVAILABLE`` if the statistics is not available on a given
178 time. Drivers should also provide the number of statistics for each type.
190 And, when the statistics got updated, set the scale::
195 .. [#f2] For ISDB-T, it may provide both a global statistics and a per-layer
196 set of statistics. On such cases, len should be equal to 4. The first
207 Groups of statistics argument
210 There are several groups of statistics currently supported:
221 typically, this statistics is always available [#f3]_.
223 - Drivers should try to make it available all the times, as these statistics
251 - Due to its nature, those statistics depend on full coding lock
260 - Not all frontends provide this kind of statistics.
262 - Due to its nature, those statistics depend on inner coding lock (e. g.
270 - Due to its nature, those statistics depend on full coding lock
277 A typical example of the logic that handle status and statistics is::
344 Driver should check such bit before making the statistics available.
381 If the driver doesn't provide a statistics available check bit
391 On such drivers, a typical routine to get statistics would be like
434 Please notice that, on both cases, we're getting the statistics using the