From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Martin Rudge <martin.rudge@googlemail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: DVB V5 API: Event Model
Date: Tue, 13 Nov 2012 07:24:14 -0200 [thread overview]
Message-ID: <50A211BE.60606@redhat.com> (raw)
In-Reply-To: <CAE-UT2ug=U4AJghXfXZBuBoa18JsPSjNsvHUEu9FHZvAm1qi1Q@mail.gmail.com>
Em 12-11-2012 11:04, Martin Rudge escreveu:
> Hello All,
>
> When using the V5 API (DVB-S/S2) for the DVB frontend device (with the
> now merged SEC functionality), setting properties DTV_VOLTAGE and/or
> DTV_TONE generates extra (unwanted?) events. This is due to utilising
> the legacy FE_SET_FRONTEND IOCTL in their respective implementations.
>
> Depending on their placement in one "atomic" FE_SET_PROPERTY call,
> they can cause an "incorrect" (premature) SYNC/LOCK event to be
> generated. For example, when looping issuing tune requests in
> succession during a scan operation. This was with a fairly recent
> media build (pulled Saturday).
I suspect that this is an undesirable behavior, likely there since the initial
version of DVB-S2 API. It could be too late to fix, as userspace apps may be
trusting on this behavior.
Maybe you could propose a patch and ask app developers what they thing about
it.
> Conversly using DTV_CLEAR clears the cached values, but doesn't affect
> the frontend (LNB). This is probably desirable behaviour.
This is desirable.
> Any thoughts, working as designed/intended?
Regards,
Mauro
next prev parent reply other threads:[~2012-11-13 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 13:04 DVB V5 API: Event Model Martin Rudge
2012-11-13 9:24 ` Mauro Carvalho Chehab [this message]
2012-11-14 9:47 ` Martin Rudge
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=50A211BE.60606@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=martin.rudge@googlemail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.