From: Jemma Denson <jdenson@gmail.com>
To: linux-media@vger.kernel.org
Cc: mchehab@osg.samsung.com,
"crope@iki.fi >> Antti Palosaari" <crope@iki.fi>,
"patrick.boettcher@posteo.de >> Patrick Boettcher"
<patrick.boettcher@posteo.de>
Subject: DVBv5 qos/stats driver implementation
Date: Tue, 05 May 2015 15:26:07 +0100 [thread overview]
Message-ID: <5548D2FF.3050100@gmail.com> (raw)
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.
next reply other threads:[~2015-05-05 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 14:26 Jemma Denson [this message]
2015-05-05 15:27 ` DVBv5 qos/stats driver implementation Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5548D2FF.3050100@gmail.com \
--to=jdenson@gmail.com \
--cc=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=patrick.boettcher@posteo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox