DVBv5 qos/stats driver implementation

Jemma Denson
2015-05-05T14:26:10Z

Mauro/Antti,

Myself and Patrick are currently in the process of bringing an old out
of tree frontend driver into shape for inclusion, and one of the issues
raised by Mauro was the requirement for the new DVBv5 stats method. I've
noticed there seems to be two different ways of going around this - one
is to run through the collection and cache filling process during the
calls to read_status (as in dib7000p/dib8000p), and the other is to poll
independently every couple of seconds via schedule_delayed_work (as in
af9033, rtl2830/2832).

Is there any reason for the two different ways - is it just a coding
preference or is there some specifics to how these frontends need to be
implemented?

Thanks,

Jemma.